Skip to content

Commit

Permalink
[Chore] Include information about content security policy in README (#23
Browse files Browse the repository at this point in the history
)
nwittstruck authored Mar 17, 2022
1 parent c490f38 commit ff65565
Showing 1 changed file with 14 additions and 1 deletion.
15 changes: 14 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -10,7 +10,9 @@ The current [entrypoint](./.docker/entrypoint.sh) will not start the phoenix ser

To start the container:
- Create a file called docker-compose.override.yml and fill in at least the `GCP_CONFIG_PATH` and a `SECRET_KEY_BASE` for app. E.g.:
```version: "3.8"

```
version: "3.8"
services:
app:
@@ -37,6 +39,17 @@ You can extract new strings to translate by running:

mix gettext.extract --merge

### Content Security Policy

You can use a content security policy to restrict which resources are being loaded. The app is completely self contained, so you can use quite strict policies. For nginx, this would look like this:

```
add_header Content-Security-Policy "default-src 'self' img-src 'self' data:; style-src 'self' 'unsafe-inline'" always;
```

There are couple of inline styles that will be removed in the future, so that ```unsafe-inline``` can be removed as well.


### Additonal licence

The qrstorage [logo](https://thenounproject.com/icon/860830/) in this repo – created by [Hopkins](https://thenounproject.com/hopkins81) – is licenced under [CC BY 3.0 Unported](https://creativecommons.org/licenses/by/3.0/).

0 comments on commit ff65565

Please sign in to comment.