Closed unmacaque closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Good catch, I'll PR a fix
Could you test lspipepr/raneto:0.17.3-pkg-6e89e859-pr-20
please, and see if it fixes the issue for you?
If you've deployed the latest version clean you will have to delete the existing config.default.js or you'll get errors related to the theme path.
Can confirm that using the image lspipepr/raneto:0.17.3-pkg-6e89e859-pr-20
picks up my configuration again. Thanks a lot for fixing!
Is there an existing issue for this?
Current Behavior
With the most recent image tag including the changes from #18, any user-supplied configuration is still ignored and Raneto always starts with the default settings.
This makes it impossible to change settings, such as content_dir to something else.
My suspicion is this was caused by this commit in ryanlelek/Raneto. With that, there is now always a default
server.js
in/app/raneto
, which means this line in docker-raneto will always evaluate to false, meaning thatserver.js
will not be copied, thus user config will not be used.Expected Behavior
User supplied configuration in
/config
should be honouredSteps To Reproduce
/config/config.default.js
and edit a configuration key, likesite_title
localhost:3000
in a browser and observe that the window/tab title has not changedEnvironment
CPU architecture
x86-64
Docker creation
Container logs