[DiscordArchive] where should i place my custom `worldserser.conf` file ? is there a relevant readme ?
[DiscordArchive] where should i place my custom `worldserser.conf` file ? is there a relevant readme ?
Archived author: neolas67 • Posted: 2023-02-26T23:20:04.938000+00:00
Original source
where should i place my custom `worldserser.conf` file ? is there a relevant readme ?
Archived author: neolas67 • Posted: 2023-02-26T23:22:11.716000+00:00
Original source
and how will we detect config changes on build time if it doesnt rewrite the file ? Do we have to build without cache or explicitly delete the `*.conf` files before build ?
Archived author: neolas67 • Posted: 2023-02-26T23:22:39.151000+00:00
Original source
I am happy to make readme updates if it doesnt exist after i understand what is the expected behaviour from user
Archived author: Nyeriah • Posted: 2023-02-26T23:25:59.328000+00:00
Original source
Just edit the file generated after compile. It will be in your release folder
Archived author: neolas67 • Posted: 2023-02-26T23:27:28.561000+00:00
Original source
what happens if the config keys themselves get changed? Is best practice, keeping a patch for default config file and reapply after each build or something like that ?
Archived author: Nyeriah • Posted: 2023-02-26T23:28:02.904000+00:00
Original source
As far as I know the file is generated once and doesn’t update afterwards
Archived author: Nyeriah • Posted: 2023-02-26T23:28:19.015000+00:00
Original source
The server will show you a warning if a config is missing
Archived author: neolas67 • Posted: 2023-02-26T23:29:17.928000+00:00
Original source
it seems like those files or owned by docker user or something getting permission issues. maybe i can look into that
Archived author: Nyeriah • Posted: 2023-02-26T23:31:29.548000+00:00
Original source
Just noticed we’re in the docker channel. Sorry no idea how it behaves in docker. But that’s what it does in a normal install
Archived author: mynameismeat • Posted: 2023-02-27T00:16:27.503000+00:00
Original source
the container runs as root