LumeWeb
/
skynet-webportal
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use `docker/kratos/config/kratos.yml` instead of `.kratos.yml`.

This commit is contained in:
Ivaylo Novakov 2021-01-13 12:46:25 +01:00
parent dc1c080f8a
commit b4d4229190
No known key found for this signature in database
GPG Key ID: 06B9354AB08BE9C6
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

@ -53,7 +53,7 @@ typings/
# dotenv environment variable files # dotenv environment variable files
.env* .env*
.kratos.yml ./docker/kratos/config/kratos.yml
# gatsby files # gatsby files
.cache/ .cache/

5
README.md
View File

@ -79,8 +79,9 @@ rs.initiate(
Most of the needed config is already under `docker/kratos`. The only two things that need to be changed are the config Most of the needed config is already under `docker/kratos`. The only two things that need to be changed are the config
for Kratos that might contain you email server password, and the JWKS Oathkeeper uses to sign its JWT tokens. for Kratos that might contain you email server password, and the JWKS Oathkeeper uses to sign its JWT tokens.
To override the default `kratos.yml` you can create ` .kratos.yml` in the root directory of the project, alongside Make sure to create your own`docker/kratos/config/kratos.yml` by copying the `kratos.yml.sample` in the same directory.
the `.env` file. Also make sure to never add that file to source control because it will most probably contain your email password in
plain text!
To override the JWKS you will need to directly edit To override the JWKS you will need to directly edit
`docker/kratos/oathkeeper/id_token.jwks.json` and replace it with your generated key set. If you don't know how to `docker/kratos/oathkeeper/id_token.jwks.json` and replace it with your generated key set. If you don't know how to

1
docker-compose.yml
View File

@ -241,7 +241,6 @@ services:
volumes: volumes:
- ./docker/kratos/config:/etc/config/kratos - ./docker/kratos/config:/etc/config/kratos
- ./docker/data/cockroach/sqlite:/var/lib/sqlite - ./docker/data/cockroach/sqlite:/var/lib/sqlite
- ./.kratos.yml:/etc/config/kratos/kratos.yml
- ./docker/kratos/cr_certs:/certs - ./docker/kratos/cr_certs:/certs
networks: networks:
shared: shared:

0
docker/kratos/config/kratos.yml → docker/kratos/config/kratos.yml.sample
View File

2
setup-scripts/README.md
View File

@ -99,7 +99,7 @@ At this point we have almost everything running, we just need to set up your wal
1. only for siasky.net domain instances: edit `/home/user/skynet-webportal/docker/caddy/Caddyfile`, uncomment `import siasky.net` 1. only for siasky.net domain instances: edit `/home/user/skynet-webportal/docker/caddy/Caddyfile`, uncomment `import siasky.net`
1. `docker-compose up -d` to restart the services so they pick up new env variables 1. `docker-compose up -d` to restart the services so they pick up new env variables
1. `docker exec caddy caddy reload --config /etc/caddy/Caddyfile` to reload Caddyfile configuration 1. `docker exec caddy caddy reload --config /etc/caddy/Caddyfile` to reload Caddyfile configuration
1. add your custom Kratos configuration to `/home/user/skynet-webportal/.kratos.yml` (in particular, the credentials for your mail server should be here, rather than in your source control). For a starting point you can take `docker/kratos/config/kratos.yml`. 1. add your custom Kratos configuration to `/home/user/skynet-webportal/docker/kratos/config/kratos.yml` (in particular, the credentials for your mail server should be here, rather than in your source control). For a starting point you can take `docker/kratos/config/kratos.yml.sample`.
## Subdomains ## Subdomains