Fix typo, change some wording.

This commit is contained in:
Hyperling 2023-07-04 09:23:07 -07:00
parent bfa6bbb2ae
commit 8fd450a483

View File

@ -1,6 +1,6 @@
# 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 practice with `docker-compose`.
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
@ -8,7 +8,7 @@ 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 ne aware that using sudo may cause file permission conflicts when interacting with the configuration files and folders.
Otherwise be aware that using sudo may cause file permission conflicts when interacting with the configuration files and folders.
Install the project dependencies.
```
@ -55,8 +55,8 @@ Compose projects are set up here. Each folder should have a `docker-compose.yml`
### 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/`.
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.