docker-palworld-dedicated-server
docker-palworld-dedicated-server copied to clipboard
Question about methods for configuration
Have you read the Important information text above
- [X] Yes i did
Current behavior
Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.
Desired behavior
Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.
Links to screenshots
No response
To Reproduce
Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.
Software setup
Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.
Hardware setup
Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.
Additional context
No response
Hello @kof8855 Because its considered Best-Practice in Docker and Docker-Compose to have your application not do that. Its called Stateless-Development with some tools, see here: https://12factor.net/config
What you would ask for is basically a "dumb-mode" not doing anything except start the server, is that right? What would be the standard start params be for that?