Skip to main content

share site among developers (version control)

Permanently deleted user

How do multiple developers work on the same Geocortex site at the same time?

I want to put a Geocortex site under version control and share the development with others.  What is the best practice to do that?

Exactly what files make up a Geocortex site that I would need to add to version control?

How do I avoid conflict when Geocortex wants to undate those files?

Please share your experiences! Thanks!

0

Comments

2 comments

Date Votes
  • Permanently deleted user

    Jen,

    I'll try to keep this short, but essentially we use GIT to store our files - in the cloud - so to speak, and then use a product called SourceTree from Atlassian to manage the files in branches - Dev and Master. All of us work in our own local copy of the Dev branch.. once satisfied - we push those changes to Dev in GIT via SourceTree.  We find this is very convenient for things such as workflows, custom files etc.. that are separate from the sites and viewer files - where we edit directly on our fileshare where we gave GE configured to point to. We do this because we can be making edits via the GE REST Manager, and this makes edits direct to the sites and viewer folders respectively, which git also keeps track of, but we don't all have copy of these two locations. We have to then post our changes back up into the Dev branch in git for our source control. This way we see the changes quickly rather than going through our deployment scripts (powershell) which look after everything from workflows, sites, viewers, xaps, dlls, map services. Eventually - everything that is stored in our Dev branch in git, is merged with our master copy and the deployment scripts are run using Hudson/Jenkins software to deploy to our DEV/UAT/TRAINING/PROD environments....

    the theory being that eveything is stored in dev versions, cherry picked to master, and rolled out so everything is identical. The powershell script do all the search and replace on server names and urls...

    it's complex, and a big step up from last year's regime of 'nothing' so we're all taking our time with it and finding it very useful. It can be a little onerous, but when we run a 24/7 application for emergency services we need that level of control built in. Bottom line is we don't ever edit Production, we do everything in Dev, and then deploy to Prod eventually once it's passed the test!

    I hope all that makes sense. But really finding GIT and Source tree very useful tools to start with.

    cheers

    GF

    0
  • Permanently deleted user

    GF,

    Thank you so much for taking the time to post this detailed answer. I really appreciate it!

    Jen

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post