-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
d2023-06-28 t06:59
- Loading branch information
Showing
1 changed file
with
20 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
version: "3" | ||
services: | ||
ewingson-css: | ||
image: ewingson/rpio-solidos:12 | ||
ports: | ||
- "0.0.0.0:3000:3000" | ||
command: "-c config-mashlib.json -f /data -b https://solid-hosting-dev.s.redhost.be/" | ||
expose: | ||
- 3000 # magic nginx, make nginx proxy know on what port our service is running internally | ||
networks: # magic nginx, we need to be in nginx's docker network so it can forward requests to > | ||
- proxy # magic nginx, this is the network named below | ||
- default # magic nginx, because we supply the new network we also need default (only needed > | ||
environment: | ||
VIRTUAL_HOST: "solid-hosting-dev.s.redhost.be" # magic nginx, where should this site be runni> | ||
LETSENCRYPT_HOST: "solid-hosting-dev.s.redhost.be" # magic nginx, where should this site be r> | ||
LETSENCRYPT_EMAIL: "[email protected]" # magic nginx, where should reports on failed letse> | ||
networks: # magic nginx, we must supply some special networks to reference | ||
proxy: # magic nginx, we name the letsencrypt proxy network "proxy" in this file | ||
external: # magic nginx, the network we will name proxy is actually an external network (meanin> | ||
name: letsencrypt_default # magic nginx, the docker network is named letsencrypt_default |