Installation and deployment
Version 7.x > Installation and deployment > Source Control and Portal Engine development model View modes: 
User avatar
Certified Developer 10
Certified Developer 10
varinder-kudosweb - 8/24/2013 6:53:49 PM
   
Source Control and Portal Engine development model
This has been discussed before

Ive been developing/maintaining pages/templates/transformations/css etc in portal engine.
However, its a little tricky when working in a team as often things get overwritten.

Is it possible to develop/test pages ( in portal engine mode ) locally and then push it to the live site?

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 8/26/2013 6:40:41 AM
   
RE:Source Control and Portal Engine development model
Hi,

Have you tried using the Team development feature in v7?

Best regards,
Juraj Ondrus

User avatar
Certified Developer 10
Certified Developer 10
varinder-kudosweb - 8/26/2013 4:51:33 PM
   
RE:Source Control and Portal Engine development model
Hi Juraj,

Thanks, this seems to be in the right direction. One question however:

Is it possible to set up a dev workflow like below?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[dev A] + [dev B] + [dev C]... -> developing pages, configuring webparts/documenttypes etc in local instance of kentico
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
||
|| -> pushing changes to github ( should this repo contain whole kentico folder? )
||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Github
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
||
|| -> *Magically* pushing staging branch commits to kentico staging server ( web hooks? https://help.github.com/articles/post-receive-hooks, id be interested to know how kentico can be setup to recieve files from a third party source control )
||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Kentico Staging site ( *Magically* in Sync with staging branch from github )
--------------------------------------------------------------------------------------------------------------------------------------------------------------------

- Varinder

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 8/26/2013 5:32:47 PM
   
RE:Source Control and Portal Engine development model
If you're using Portal Engine and you don't have code changes/additions, GitHub will be useless because all your page templates, layouts, documents, transformations, etc. will be directly in the database.

If you plan to maintain this site after the deployment, I recommend putting the whole website in a repository. This way when you use the KIM tool to update your site you can check those files into your repo and keep track of items that were updated. Here is a pretty good thread that talks about source control and Kentico.

User avatar
Certified Developer 10
Certified Developer 10
varinder-kudosweb - 8/26/2013 5:50:07 PM
   
RE:Source Control and Portal Engine development model
Hi FroggEye,

I could've revived that thread instead of starting a new one.

Im sorry im confused ( maybe im thinking too far before actually doing anything )

- Portal engine changes are directly in the database.
- So i'd go ahead and export pagetemplates etc to CMSVirtualFiles?
- ... crap, i have no idea what im talking about

Well, sorry back to the lame question: how would i go about using a source control in portal engine development model (i.e, all the files are actually in db of local kentico installation)?

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 8/26/2013 10:01:38 PM
   
RE:Source Control and Portal Engine development model
Hi,

I believe that the idea is to use the virtual files on file system just like in deployment mode. In portal engine the objects we are talking about are virtual - they are stored in the database.

Regrettably, there is no workflow for objects but it will be added soon. Right now, only object versioning is available.

Best regards,
Juraj Ondrus