Re: Docker container added for Roundup

In message <[email protected]>,
SCHLEMMER Norbert writes:
>Just a short sum-up: The container is "up and running" ... great!

Yeah!!

I have committed patches that allow roundup to find the locale and
template files within the wheel install directories. See:

 https://issues.roundup-tracker.org/issue2551167

I will also be adding a source=local-pip build-arg option for the
Dockerfile.  This installs the local source files in wheel format
using pip. It uses pip install but doesn't copy the man pages,
templates, locale files outside of python's site-package directory. I
used it for testing my changes for issue2551167.

>To use and test the mysql or postgresql backend : the backend is part

If you mean the mysql and postgresql client libraries for the backend
yes.

>of the roundup-app container but the database have to be running as
>separated container, isn't it ?

Yes, that is my understanding of docker best practices. IIUC the
database and the dockerized roundup can connect over the internal
docker network so the database never binds a port to an external
interface on the host computer.

IIUC is also possible to bind the database to the docker network
gateway IP (172.17.0.1 on my system) on the host system. That port can
be used without the database server being accessible from outside the
host system. But I don't think this is docker best practice.

>Maybe, will test and provide a docker-compose yml file... 

That would be great. When I wrote the article on roundup for LWN
(https://lwn.net/Articles/869118/), one of the comments was that there
was no docker-compose/containerized deployment for it.  Hopefully we
can chip away at that issue.

Thanks for your help and testing. Have a great day and stay safe.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.