docker-scripts is a framework that uses bash scripts to create a unified CLI for common tasks of cloud apps, like: installation, update/upgrade, backup/restore, etc. It tries to make easy self-hosting of web-apps and web-services on a cloud server.
docker-scripts is quite convenient for personal/family usage or small organizations, which don’t have lot’s of users and high loads, and therefore would like to optimize the resources required (and the costs) for hosting these applications.
Unlike other alternatives (like YunoHost, FreedomBox, TurnKeyLinux, NethServer, etc.), which promise an easy management of the apps with just a few clicks (from a web GUI), docker-scripts promises an easy management with just a few commands (from the terminal). So, instead of isolating the users from Linux and from the command-line, docker-scripts tries to encourage them for using the commands and bash scripting. The users can leverage the power of Linux commands and bash scripting to adapt and better integrate with each-other the applications that they install.
The aim of this category/community is to facilitate discussions about docker-scripts, including questions or asking for help if something does not work as expected. It also serves for notifying users about important modifications or improvements to the scripts. Anyone who is using docker-scripts should join this community, to keep up-to-date and to get support.
NOTE: How is docker-scripts related to LUGBZ?
For those who don’t know, the applications that are installed on the LUGBZ server (Postfix, WordPress, NextCloud, Discourse, Mastodon, etc.) are based on docker-scripts. So LUGBZ is one of the users of docker-scripts.