zedcode/selfhosted-apps-docker
1
0
Fork 0
mirror of https://github.com/DoTheEvo/selfhosted-apps-docker.git synced 2026-07-03 14:06:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
DoTheEvo
2023-03-20 19:54:20 +01:00
parent 390a146999
commit c823658ee1
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -8
View File
@@ -47,16 +47,16 @@ Repo documents self hosted apps in similar format and also uses caddy for revers
# Core concepts
- `docker-compose.yml` do not need any editing to get started,
changes are to be done in the `.env` file.
- Not using `ports` directive if theres only web traffic for a container.<br>
Theres an expectation of running a reverse proxy which makes mapping ports
to a docker host unnecessary. Instead `expose` is used which is basically
- **docker-compose.yml** does **not** need any **editing** to get something up,
**changes** are to be done in the **.env** file.
- **Not using** `ports` directive if theres **only** web traffic for a container.<br>
Theres an expectation of running a **reverse proxy** which makes **mapping ports**
to a docker host **unnecessary**. Instead `expose` is used which is basically
just documentation.<br>
- For persistent storage bind mount `./whatever_data` is used.
- For **persistent** storage **bind mount** `./whatever_data` is used.
No volumes, nor static path somewhere... just relative path next to compose file.
- no version is declared in compose, as the practice was
[deprecated](https://nickjanetakis.com/blog/docker-tip-51-which-docker-compose-api-version-should-you-use)
- **no version declaration** at the beginning of **compose**, as the practice was
[**deprecated**](https://nickjanetakis.com/blog/docker-tip-51-which-docker-compose-api-version-should-you-use)
---