From: <iva...@ri...> - 2023-11-07 00:35:18
|
Hello John! On 2023-11-06 23:13, John P. Rouillard wrote: > > BTW we have docker images at hub.docker.com look for Roundup. Thank you. I prefer CI tools and Git for delivering and updating web applications. > Try this. Set the environment variable: > > PGSERVICE=your_service_name > > Then remove any values for the settings: > > host, port, user, password, and name > > in the rdbms section of the tracker's config.ini. (If you are not > setting some of those values in your pg_service.conf, set them in > config.ini.) Make sure the rdbms backend setting is set to postgresql. > > If your pg_service.conf file looks like: > > [roundup_roundup] > host=127.0.0.1 > port=5432 > user=rounduptest > password=rounduptest > dbname=rounduptest > > (the defaults for demo mode), run: > > roundup-admin -i tracker_home list status > > and see if you get a connection error. Excellent! Thank you very much. I will try it. > psycopg2 looks like it can use a "service=service_name" in its connect > method. (Working from https://github.com/psycopg/psycopg2/issues/926.) Django can use psycopg2/psycopg3 in a similar way. Since version 4.0, you can simply use the service parameter to connect to PostgreSQL without even specifying the database name. If you are interested, details can be found here: https://code.djangoproject.com/ticket/32292 > It might be a useful enhancement to support 'service' directly in > config.ini. It would be useful when running one roundup server serving > multiple trackers. > > If you want to move forward with Roundup and run multiple trackers > with one Roundup server instance, we can work on getting support for > specifying the 'service' in config.ini. You would need to test using > the current development code. Thank you. At the moment I plan to install only one tracker, but I think it would be nice to have such an option. When you implement this, I will be happy to test it. > Let me know how this works for you. Well, of course. -- With appreciation, Ivanov |