Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: document DNS configuration #27

Merged
merged 1 commit into from
Jan 23, 2024
Merged

docs: document DNS configuration #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,3 +187,22 @@ docker-compose up -d
cd ~/
```

## DNS configuration

We use terraform for the configuration of our DNS rules on the cloudflare platform, the configuration is
available in the `terraform` folder, which anyone can use to configure their own DNS rules for the app,
provided they change the secrets to point to their own respective accounts.

As for the actual configuration itself, the application requires a simple A record pointing to the server's IP address,
defined as below (for the `api.dai.heig.lutonite.dev` domain):

```
api.dai.heig.lutonite.dev. 300 IN A 185.144.38.63
```

In cloudflare, we disabled the proxy since we are using traefik to handle the SSL certificates, as
well as the redirection to the proper services, and we didn't want cloudflare to intervene in the TLS chain.

We have added additional domain names all pointing to the same IP address for access to the whoami application
as well as the traefik dashboard.

Loading