pyx volume empty, override properties not used. about dockeryourxyzzy HOT 5 CLOSED

changed the RUN in the dockerfile to include:

 && cp build.properties.example build.properties.a \
 && cat build.properties.a /overrides/build.properties > build.properties \

and prepended this to the CMD:

cat build.properties.a /overrides/build.properties > build.properties && 

it seems to work, but i configured it to use postgres as a database, the only issue being that the postgres database is empty, so all the queries fail...

edit: importing the cah_cards.sql seems to have worked, tho it should be noted that the docker compose file, as it is in this repo, is running a postgres container for nothing, since by default sqlite is used and postgres cant just be enabled in the config

from dockeryourxyzzy.

I wonder if the latest Dockerfile refactor deprecated overrides/build.properties. Can you get any overrides to work if you specify them in CMD a la https://github.com/emcniece/DockerYourXyzzy#run-with-overrides ?

from dockeryourxyzzy.

Yeah, it looks like the overrides directory is added (https://github.com/emcniece/DockerYourXyzzy/blob/master/Dockerfile#L22) but nothing is done with it after the fact.

Perhaps entrypoint.sh should append the overrides to the main build.properties on startup...

from dockeryourxyzzy.

would appending the overrides work? i dont know how the build.properties is read, so im unsure whether duplicate lines would cause issues, but if its as simple as appending, i can figure something out.

from dockeryourxyzzy.

it also seems that i was mistaken, the .pyx volume is not meant to contain the containers /project, its supposed to contain /output which is empty in the container, and im unsure what the purpose of that is

from dockeryourxyzzy.