Best practice for version control on a site

Robert Driessen

12. Dezember 2018 23:28

Hello

 

Is there an accepted best practice for managing versions for a site and viewer. 

 

What is the best way to backup a site and then recover that site if required.  I just copied a site in Geocortex essentials manager which appears to work but when I open the viewer for the backup site I get a ConfigurationLoadFailed/RequestError (Desktop.json.js status: 500).  So that doesn't seem reliable.

0

• 

  Tom Neer

  13. Dezember 2018 16:45

  There is no "best practice". I would suggest the following, which we have used:

  • Simplest - When manually editing site.xml or desktop/tablet/mobile.json.js copy and rename the file with a date (e.g. Site.xml.20181213)
  • Enable Shadow Copy/VSS on your Sites folder
  • Github. If you go this route, there is no integration so you would make your changes in the REST Manager, then have to to push using GIT command line or Github Desktop. Note: If you backup your viewer, this will exceed the 1000 file limit in Github Desktop, so you will need to use the command line for the initial seed.

  Pretty much, use whatever method works best for you. But it will be a multi-step process. The good thing is that the next-gen Geocortex Web Viewer has version control built into the Manager. We are really excited for this feature. 

  0
• 

  Tom Neer

  13. Dezember 2018 16:45

  Oh, and have offsite backups as a complete fallback. =)

  0
• 

  Robert Driessen

  2. Januar 2019 22:54

  Thnaks Tom, you comments are much appreciated!

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.