Servoy Developer catastrophe

Questions and answers for all installation-related topics for Servoy products

Servoy Developer catastrophe

Postby Westy » Mon Dec 03, 2018 6:46 pm

Fortunately, we have never had a Servoy Developer catastrophe. However, we want to be sure we fully understand all the pieces necessary to reconstruct a Servoy Developer server.

What exactly does the servoy_repository do in a Servoy Developer only installation?

In the event of a catastrophe can Servoy solutions be restored only using the contents of the servoy_workspace folder, or is a copy of the servoy_repository also needed?

Dean Westover
Choices Software, Inc.
Westy
 
Posts: 844
Joined: Fri Feb 13, 2004 5:27 am
Location: Lynnfield, Massachusetts USA

Re: Servoy Developer catastrophe

Postby jcompagner » Mon Dec 03, 2018 7:04 pm

there is not really a "developer server"
but in repository doesn't do much in a developer anymore. You could even work with the developer without that whole database.

All sources (your workspace) should be a in GIT or anything like that. (so under version control on a server)
But yes the workspace is always your latest copy
Johan Compagner
Servoy
User avatar
jcompagner
 
Posts: 8124
Joined: Tue May 27, 2003 7:26 pm
Location: The Internet

Re: Servoy Developer catastrophe

Postby sean » Mon Dec 03, 2018 7:24 pm

Hi Dean,

Also a good practice to make a "Tag" in your source control system that corresponds to a given build.
Then you know, from which point in your revision history, to generate a build that is exactly the same as the one you have in production.
Software Engineer
Servoy USA
sean
 
Posts: 128
Joined: Mon May 21, 2007 6:26 pm
Location: USA

Re: Servoy Developer catastrophe

Postby Westy » Mon Dec 03, 2018 9:50 pm

Thank you Johan and Sean.

Dean
Westy
 
Posts: 844
Joined: Fri Feb 13, 2004 5:27 am
Location: Lynnfield, Massachusetts USA

Re: Servoy Developer catastrophe

Postby goldcougar » Wed Dec 05, 2018 5:08 pm

What we do:
- Follow good source control practices. We've adopted GitFlow and I highly recommend it.
- Don't forget about your non-servoy source code dependencies. Like plugins, extra files in the application_server/server/webapps/ROOT folder. Also your servoy properties files, Jasper reports, etc. Make sure they are all under source control. We add plugins and other dependencies into source control, and then use an ant script so each developer can run it, and it installs all the proper dependencies into their installation.
- Make sure your production repository database is backed up. In event of server catastrophe, restoring that will restore all your source
- If you have a code signing cert you use, make sure its backed up someplace safe too.

PS. to answer your question about getting source from the repository...Yes, that is also possible, but not desired and a pain to do. The option on the application server to use a team provider. Its not recommended, but is a possible fail-safe that I've had to use before (old developer left a company, and didn't use source control). https://wiki.servoy.com/display/DOCS/Se ... m+Provider
Scott Butler
iTech Professionals, Inc.
SAN Partner

Servoy Consulting & Development
Servoy University- Training Videos
Servoy Components- Plugins, Beans, and Web Components
Servoy Guy- Tips & Resources
ServoyForge- Open Source Components
User avatar
goldcougar
Servoy Expert
 
Posts: 668
Joined: Sun Jan 08, 2006 7:15 am
Location: Cincinnati, OH


Return to Installation

Who is online

Users browsing this forum: No registered users and 1 guest

cron