In servoy 3.5 I have a local DB with a local repository and example data table. When I have tested my solution I export the .servoy file and I upload it via web interface on the production server (with its production repository and production data) and I create a new local release. (I make this operation also when I discover a bug after few minute of deploy the production release so the release number increse very fast)
I don’t fully understand on servoy 4.0 what’s the best solution for this cycle.
I suppose this, but I’m not so sure… (I’m not so sure also on 3.5 ![:?]( "Confused")
)
Only a clean repository in production server. Import all the 3.5 solutions via web interface. Checkout all the solution in eclipse workspace.
So in develop environment I have in “Database Servers” the production repository and a series of local example data database.
After I made my develop and test (in my workspace) I apply the changes to the develop repository making a commit.
And the release number? I have to change that only when I made a big develop step for handle clients activate solutions?
I didn’t simply undestand nothing from the 3.5 cycle?
Sorry for my english…
You can go about it many ways, but this would work in your setup:
1 Production environment, running a Servoy Application Server and dedicated production databases.
1 Development environment: Servoy 4.0 Developer + dedicated test databases (Copies of your production databases).
Comming from 3.5, you would do the following steps:
- Export your solutions from 3.5 using servoy Developer 3.5
- Setup 4.0 Application Server connected to your production databases and import the 3.5 export files through the admin pages. (Production environment ready)
- Install Servoy Developer 4.0 locally on your machine, make a copy of your production databases and install them locally and hook up the databases to your local developer. Import the 3.5 solution files using the Admin pages of your local developer. Then checkout the Solutions from your local repository into your local workspace. (Developer environment ready)
From now on, you develop and test locally in your development environment. When you’re done developing and testing, you commit to your local repository. If you want (because you made big changes) you can create a new release of the involved solutions through your local admin pages. When you want to push a version into production, you export from your local workspace (File - Export - Servoy - Export Active Solution). This will give you a .servoy file again, which you can import into your production environment using the admin pages of your production environment.
Note: when working as a stand alone developer and exporting from your local workspace as described above, there is technically no real reason to commit any changes to your local repository, but it’s considered good practize to do this anyway (then you have 2 copies: your local workspace (files on disk) and your local repository (database).
When you work with multiple developers, you do need to commit all your changes to a repository, but in this case you need to set up a central repository to which all Developers connect to commit their changes.
Hope this helps,
Paul