I have a question for you all regarding modules and import/export of solutions.
We are an FDA regulated facility in the US, so our active solution needs not be altered in any way once we go live, even the back-end tables until a full validation/testing is completed.
However, we need to constantly make changes/bug fixeds/improvements/add new interfaces to the solution. What is the best way to be able to make changes, validate/test it “offline” and then roll out the latest revision on the live server?
I know servoy has some built in functions to allow for that but I think there’s some inherent problems with it or I’m not understanding it fully.
A) Revision control: I know with Servoy, I can take out a new revision, work on the new revision until it’s ready to be “active.” However, I don’t think I can 1) test it out as a client, 2) I’m actually adding fields to our existing live server
B) Using a module on a 2nd computer, 2nd install of servoy/sql server. I can work on a new module, then just import the module to the live server once my testing on my 2nd computer is complete. However, what happens if I need to create a new module AND modify the existing solution as well?
c) create a snapshot of my live server. Import the entire snapshop into 2nd computer, work on the solution. Then take that entire snapshot of the 2nd computer and bring it back to the live server. (will all the data automatically link up?) . this probably will work best I think right?
Any suggestions or solutions will be great. I might be wrong on some of my servoy assumptions. Still learning :>
Create you solution on the developer and export it to your server. Create a new release and export it again…
On top of that, when a user has an issue I can’t reproduce on my system or there is something going on in the live data I pick up their last db’s and test with that data. Remember to do that on another developer or otherwise you will lose your latest release that you are working on.
To my knowledge this is rocksolid. Work like this for nearly 2 years now (march or april I believe) on a highly critical production environment.
Now, our IT guys are not playing nice. They would like me to stick with 1 computer (because we use MS SQL server 2000). They said I should just create another instance of the database in Sql server and off we go.
Can we go back and forth (test and live environment) on the same machine? How can we make the test clients only log on to the test enviroment and everyone else log on to live environment.
I’m so worried about data corruption, mix ups, etc. I remember Bob Cusick had like 7 instances of servoy installed on his laptop. please shed some light on the best way to do this? i’m still a bit confused and nervous about this.
Why don’t you just do your development with the standard iAnywhere db’s. As long as you name the db servers with the same name there is no need to develop on a mssql db. That’s one of the nice things about developing with Servoy
sammyzheng:
I’m so worried about data corruption, mix ups, etc. I remember Bob Cusick had like 7 instances of servoy installed on his laptop. please shed some light on the best way to do this? i’m still a bit confused and nervous about this.
I’m on a Mac and I have one instance of Servoy for each project I’m working on – in fact 2 for each project, since I have separate Servoys for Development and Deployment I have stripped out all unneccesary database connections.
No need to think in the morning, just launch the servoy with some “projectname”.
I have stripped out all unneccesary database connections.