affine/pathfinder-containers
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #20 from ajaxify/add-lets-encrypt-email-env-var

Browse source 
Add lets encrypt email env var
This commit is contained in:
Sam 2022-08-28 00:08:42 +02:00 • committed by GitHub
commit 827f24f626
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.env.example
View file

@ -1,6 +1,8 @@
PROJECT_ROOT="" PROJECT_ROOT=""
CONTAINER_NAME="pf" CONTAINER_NAME="pf"
DOMAIN="" DOMAIN=""
# Emails from Let's Encrypt about your certificate will go here
LE_EMAIL=""
APP_PASSWORD="" APP_PASSWORD=""
MYSQL_PASSWORD="" MYSQL_PASSWORD=""
CCP_SSO_CLIENT_ID="" CCP_SSO_CLIENT_ID=""

2
README.md
View file

@ -89,7 +89,7 @@ A fork of techfreak's [Pathfinder-container](https://gitlab.com/techfreak/pathfi
docker-compose exec pfdb /bin/sh -c "unzip -p eve_universe.sql.zip | mysql -u root -p\$MYSQL_ROOT_PASSWORD eve_universe"; docker-compose exec pfdb /bin/sh -c "unzip -p eve_universe.sql.zip | mysql -u root -p\$MYSQL_ROOT_PASSWORD eve_universe";
1. **When everthing works, configure Traefik correctly for production** 1. **When everthing works, configure Traefik correctly for production**
* Remove the beta CA server lines [(#87 - #90)](https://github.com/goryn-clade/pathfinder-containers/blob/master/docker-compose.yml#L87-L90) from `docker-compose.yml`. * Remove the staging CA server line [(#89)](https://github.com/goryn-clade/pathfinder-containers/blob/master/docker-compose.yml#L89) from `docker-compose.yml`.
* Delete the `./letsencrypt/acme.json` configuration file so Let's Encrypt will get a new certificate.</br></br> * Delete the `./letsencrypt/acme.json` configuration file so Let's Encrypt will get a new certificate.</br></br>
* If you are not the root user on your host you may need to edit file permissions. Docker-engine creates the `letsencrypt` director as root user, which means that you would need to prefix `sudo` on any future docker commands (`sudo docker-compose up` etc). To avoid doing this you can take ownership of the letsencrypt directory by running `sudo chown -R $USER ./letsencrypt`. * If you are not the root user on your host you may need to edit file permissions. Docker-engine creates the `letsencrypt` director as root user, which means that you would need to prefix `sudo` on any future docker commands (`sudo docker-compose up` etc). To avoid doing this you can take ownership of the letsencrypt directory by running `sudo chown -R $USER ./letsencrypt`.

2
docker-compose.yml
View file

@ -87,7 +87,7 @@ services:
- "--certificatesresolvers.letsencrypt.acme.storage=/letsencrypt/acme.json" - "--certificatesresolvers.letsencrypt.acme.storage=/letsencrypt/acme.json"
# Remove below line when ready for production # Remove below line when ready for production
- "--certificatesresolvers.letsencrypt.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory" - "--certificatesresolvers.letsencrypt.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory"
- "--certificatesresolvers.letsencrypt.acme.email=MYEMAIL@someemailprobablygmail.com" - "--certificatesresolvers.letsencrypt.acme.email=${LE_EMAIL}"
ports: ports:
- "80:80" - "80:80"
- "443:443" - "443:443"