Chad f56b3da23d
Manage Script, Resource Limits, OnlyOffice Changes (#14)
* Create explicit file for cron, add two automations from fixes.

* Merge the OnlyOffice project into the Nextcloud project. Enhance comments and changelog. Make the container names consistent.

* Found the link. :)

* Add more variables.

* Add a TBD file for mail server.

* Create new script which will replace most the existing single purpose management scripts.

* Add limit to DNS so that if Internet goes out it does not max system resources.

* Prevent OnlyOffice from getting too hungry.

* Ensure Reverse Proxy always has at least some resources.

* Separate build. Add stats -s and combination option -A.

* Make script config file aware. Add comments.

* Add more comments.

* Fix comments.

* Further determine resource allocations.

* Also avoid checking for cron's call to the program.

* Add clean and log parameters. Some clean up.

* Update setups to have DIR first.

* Remove files taken over by manage script.

* Cleaning comments and output.
2023-09-01 05:50:29 -07:00
2022-08-06 07:52:11 -05:00

My Docker Setup

Scripting my way into the Docker world. I was unable to find a good tutorial on using and managing containers so this is what made sense to me based on practice with docker-compose. I am still new-ish to Docker and am likely to make mistakes, but you're welcome to learn with me. ;)

Disclaimer

Currently the project only focuses on apt based operating systems.

Other README's

Each ./Config/PROJECT/ folder also contains its own README file with specific information to running that sub project. This file's job is to cover the general Docker installation. The others then contain details on their program setup.

How To Use

Most of these commands benefit from being root. Something like a sudo su - if you feel comfortable with it. Otherwise be aware that using sudo may cause file permission conflicts when interacting with the configuration files and folders.

Install the project dependencies.

apt install git bash

Clone the project. You may choose anywhere, but /opt/Docker is recommended.

git clone https://github.com/hyperling/docker /opt/Docker

Load the environment variables.

source /opt/Docker/source.env

Install docker to the system using the official repos.

install.sh

Create an area to add a new product.

create.sh PROJECT_NAME

Edit the project's details.

vi /opt/Docker/Config/PROJECT_NAME/docker-compose.yml

Start all of the docker projects.

start.sh

Cross your fingers and hope to profit!

Folders

Config

Compose projects are set up here. Each folder should have a docker-compose.yml file set up.

Volumes

The data of the files go here if the Config is done correctly. I think this should be easier to remember than /var/lib/docker/volumes when it comes time for migrations. Hopefully all that'd be needed is to rsync /opt/Docker and run install.sh and then start.sh on the new server. You are welcome to use a directory other than /opt/Docker, this project is location agnostic.

bin

Scripts to help make life easier. Some are pretty basic, but others do nice things like handle the container IDs.

  • install.sh : Install dependencies on a new server with apt.
  • create.sh : Create a new folder with the needed yml file.
  • start.sh : Start all compose containers.
  • stop.sh : Stop all compose containers.
  • get_logs.sh : Create log files rather than using the docker log command or searching in /var/whatever.
  • uninstall.sh : If something goes wrong and you'd like to start from scratch without provisioning a new server then this should do the job.
Description
docker-compose setup with an abundance of scripts. Setups for Nextcloud, OnlyOffice, a reverse proxy, DNS server, dynamic DNS maintainer, etc.
Readme
Languages
Shell 68.4%
DIGITAL Command Language 24.9%
Dockerfile 6.1%
HTML 0.6%