chore: update the doc and config file

[wood-push-melon]

This pull request updates docs

[shipperizer]

albeit this is technically a reasonable thing to do I'm not sure it s the best one

i would expect that if I run the rock without anything it starts up and gives me a minimum working glauth server, is that the case if we remove the config? can glauth start without a config file?

[wood-push-melon]

albeit this is technically a reasonable thing to do I'm not sure it s the best one

i would expect that if I run the rock without anything it starts up and gives me a minimum working glauth server, is that the case if we remove the config? can glauth start without a config file?

Nope. If we purely run the container without mounting a config file, it will not start the service. The reason I removed it is that the charm no longer needs it and we have to maintain a copy of the config file (If something is changed in the upstream for the config, we have to remember to come here to check and modify it if needed.)

[shipperizer]

albeit this is technically a reasonable thing to do I'm not sure it s the best one
i would expect that if I run the rock without anything it starts up and gives me a minimum working glauth server, is that the case if we remove the config? can glauth start without a config file?

Nope. If we purely run the container without mounting a config file, it will not start the service. The reason I removed it is that the charm no longer needs it and we have to maintain a copy of the config file (If something is changed in the upstream for the config, we have to remember to come here to check and modify it if needed.)

i would proabably keep it then, we are supposed to build off a tag or specific commit, so on source change we would have to double check the config

happy to go with whatever the team decides though, let's discuss at standup