[WIP] Add Podman Quadlet deployment instructions to README#63
[WIP] Add Podman Quadlet deployment instructions to README#63monospacedmagic wants to merge 2 commits intodeinfreu:mainfrom
Conversation
Added deployment instructions using Podman Quadlets with example configuration files.
|
As I mentioned in #62 (comment) I want to add to the docs in this PR as well, however that would extend the scope of this PR. I think it's worth considering to link to the docs instead then, to not spend so much README space on something that is commonly considered an alternative deployment method to Docker, as much as I want to promote it personally. What do you think? I'll set this PR to WIP for the time being, if I'm able. |
|
Hi, the You may also want to set a Furthermore I stumbled over the fact that anything in the env file that deals with Strings in the HYTALE_* Keys must not be quoted, probably an issue in After some experimentation you also need to consider, that the Server needs to be started with The Compose Docs assume you're running in Attached mode on first run, which isn't possible with quadlets AFAIK: |
|
Hi! Thanks a lot for your work on this, much appreciated @monospacedmagic. I’m not going to merge this PR. The reason is that I want to keep the README.md clean. only the quick start and a small FAQ belong there. That said, these instructions are perfect for the documentation. We can create a new page under the /technical Technical Info menu, or I can create a new Alternative Setups section, since I’d also like to include more information for TrueNAS SCALE and Unraid. |
|
@deinfreu I'll change this PR to add to the docs instead then. I'd say we can just do a whole |
|
@monospacedmagic good thought. It is best I create a notice on the top of these instructions with a reference to the Podman installation method. This is the best way to make sure the Podman installation method has the best visibility. Also a notice with a link on the README.md and DOCKERHUB.md is good. |
This adds the basic rootless Podman Quadlets example from #62 to the README, if that's something you want, as a separate PR for your convenience.