I’m a coder rather than a sysadmin, and I’m struggling to get this done as the documentation for this scenario seems somewhat thin.
WHAT I WANT TO DO:
Developer installed on a local windows box.
Server and repository on a remote, headless CentOS Linux box.
Metadata and data on a Postgres server on the remote box.
WHERE I’VE GOT TO
Run the install on a local Linux box and copied the Servoy directory over, as suggested in the docs.
Got Developer on the Windows box talking to Postgres on the remote box via SSH Tunnel (disappointing that there’s no built in tunnelling).
MY UNDERSTANDING OF THE NEXT STEPS
Set up repository and other meta data databases in the Postgres DB
Manually edit servoy.properties on the remote box
Run the server startup shell script on the remote box
WHAT I’M STUCK WITH
Assuming I’m on the right track, I’m probably being dim but I can’t find any documentation for step 1 - setting up the meta-data in Postgres. How do I generate the data structure for the appserver to connect to?
Once I’ve set up the data and edited the properties, is there any reason why things shouldn’t work?
I’ve spent rather more time on this than I can sensibly spare, so I’d very much appreciate some help!
But unless I’m missing something there is a bootstrapping problem, because without a db server in the repository for postgres, Servoy can’t connect to postgres to create the new repository? So on another thread I’m trying to get my install working with the default repository, and then I’ll try to make the switch to postgres.
If I can get iAnywhere running, postgres would be a luxury, but I’d much prefer to have only one database to worry about and back-up, if possible…
gcaplan:
without a db server in the repository for postgres, Servoy can’t connect to postgres
The db servers that servoy uses aren’t saved in the repository, but in the servoy.properties file. So first you have to edit your properties file so that it has a connection to the db in postgres that will become the repository db. The serverName of that connection should be “repository_server”.