-
Notifications
You must be signed in to change notification settings - Fork 994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docker-compose as an installation method to the docs #457
Comments
This will never stop and only move from X to having Y problems with Z, especially once addons/themes are involved with the way images are built right now. It was planned for the new documentation rewrite for V2, but since that's stagnated, I'm not sure if @matthewpi is still taking the lead on that or not. The plan was/is to provide an option for the user to choose the method of installation and distro on the main page, instead of only showing Ubuntu and hiding the rest in the community section. There is a guide hidden in the docker folder and linked in the Discord channel pinned messages |
In any case, yeah, it just needs to get added to the docs in a way that makes sense |
The complete lack of documentation about the panel and wings docker images makes it very difficult to set this up using docker. There is basically no information about which environment variables are used and which directories should be mounted for persistence. The repositories even hide the Packages section for some reason, so new people will not even see that official docker images exist at all. |
Thats actually not entirely true. There are example compose files in each repo, and support channels way at the bottom of the discord server Its certainly not great for discoverability |
Adding docker-compose as a method of installation to the documentation could be a great way to install the panel for the less technically inclined people, who would otherwise use scripts and clog up the support channels.
Currently, only people who know what they are looking for would use the images, and they are people who could install the panel normally anyway, which isn't really taking full advantage of the utility of docker containers
The text was updated successfully, but these errors were encountered: