Chad
3c46dfec01
* Add new area for defining upstream systems. * Example file for demonstration domain. * Use the new upstream hosts section. * Do the proxy directives in the main file. * Commit any final changes. * Fix example resource name. * Mention the need to have ports specified in the upstream file, not server block. * Adjust formatting.
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 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.
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.
git clone https://github.com/hyperling/docker /opt/Docker
Load the environment variables.
source /opt/Docker/source.env
Install docker to the system.
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.
That's my opinion though, if someone else uses this then they are welcome to place it where they'd like.
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 thedocker logcommand 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.