Flushing servoy modules

Classic Servoy
1

When I change a solution, I commit the changes and then I flush de solution in the server administrator. But what about modules? I commit the changes, flush the module and then flush the solution. These two steps are neccesary or can I simply flush the solution?

Thanks

2

Why are you flushing the solution/modules ? This is your teamserver, right ?
For other developers to see your changes you don’t have to flush anything. They can simply synchronize and they see the changed objects.

3

you don’t need to flush solutions from the admin page,
when you are using the server as teamserver

4

Gabi Boros:
you don’t need to flush solutions from the admin page,
when you are using the server as teamserver

So if I do changes in a soution (and I commit them), when a user starts the client he sees tha changes without flushing the solution? :shock:

5

It’s not recommended to use the teamserver as a test-, or worse, as a production server.
Just setup another Servoy Server instance connected to it’s own repository database and export your solution from your workspace and import it into the test/production server via the servoy-admin pages.

6

if you are using it as team server, then you should not run
any client from that server, but use it only for sharing the source code for the solutions;

7

ROCLASI:
It’s not recommended to use the teamserver as a test-, or worse, as a production server.
Just setup another Servoy Server instance connected to it’s own repository database and export your solution from your workspace and import it into the test/production server via the servoy-admin pages.

Wow, I’m a bit confusing… I have to make 2 or 3 changes in my solution every day; if I export the solution and then import it into the server, I’ll have hundred of releases!

8

Maybe you can explain a bit more what you are actually doing.
Who is using the clients on that teamserver for example. Just you for testing ? Or other developers/testers for testing? Or is it indeed a production server ?

9

Ok.

There’s one developer (me :wink:) and the teamserver is also the production server, so the users connect to that server to start the client. As I have noted, I have to do many changes every day in the solution. What are the “best practices” in my case, then?

Thanks

10

Your case doesn’t exist in the ‘best practices’ because it’s not one ;) .
Best practice would be to export from your developer and import into the production server. But if you really want to go this (not recommended) route then, in my experience, it’s better to reboot the Servoy server after you did a commit than to flush the solution/module. Especially when you altered some tables.

Hope this helps.

11

Ok, thanks