You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2024. It is now read-only.
The most common issue with SkinSystem is that the system doesn't work because of some dependency issues, be it incorrect PHP setup, missing PHP modules, etc..
From here on "bare-metal" means "hosted without any additional abstraction layers - eg. docker" and "directly on the host operating system" but not "directly on host hardware" as in the context of operating systems.
I'd like to suggest that we move from the "bare-metal" to Docker based installation first, meaning the the officially supported setup would be via Docker install.
Configuration options would be passed via environment variables - best (and most consistent way of doing this is by using docker-compose definition files, or via bash scripts ofc).
Improvements over current setup:
Many server communities are now running their servers using Docker, a good example for docker-based game server panel is pterodactyl.
Github provides their own container registry ( ghcr.io ). Container images can be build directly using CI (github actions) and pushed to the registry.
Updating wouldn't be a hassle, just restart the container and you good.
No issues with PHP dependencies and stuff as it'll be all "builtin" already
The project would still support direct installs to a webserver, eg. shared web hosting.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The most common issue with SkinSystem is that the system doesn't work because of some dependency issues, be it incorrect PHP setup, missing PHP modules, etc..
I'd like to suggest that we move from the "bare-metal" to Docker based installation first, meaning the the officially supported setup would be via Docker install.
Configuration options would be passed via environment variables - best (and most consistent way of doing this is by using docker-compose definition files, or via bash scripts ofc).
Improvements over current setup:
The project would still support direct installs to a webserver, eg. shared web hosting.
The text was updated successfully, but these errors were encountered: