38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# My Docker Setup
|
|
Scripting my way into the Docker world.
|
|
Was unable to find a good tutorial on using and managing containers so this is what made sense to me based on practicing with `docker-compose`.
|
|
I am still very 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
|
|
`apt install git bash`
|
|
`git clone https://github.com/hyperling/docker /opt/Docker`
|
|
`source /opt/Docker/source.env`
|
|
`install.sh`
|
|
`create.sh PROJECT_NAME`
|
|
`vi /opt/Docker/Config/PROJECT_NAME/docker-compose.yml`
|
|
`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's needed is to rsync `/opt/Docker` and run start.sh on the new server.
|
|
That's my opinion though, if someone else uses this then they can use `/var/`.
|
|
|
|
### 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.
|