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

Jump to bottom

Deploy using Kamal #145

Merged
merged 14 commits into from
Aug 23, 2024
Merged

Deploy using Kamal #145

merged 14 commits into from
Aug 23, 2024

Conversation

santiagorodriguez96
Copy link
Contributor

Motivation

This PR configures kamal so that we can start using it for deploying to our AWS servers.

Details

You will need an .env file with these secrets SECRET_KEY_BASE and POSTGRES_PASSWORD

Steps to set up the servers in AWS:

  1. Run this to install docker
sudo apt update
sudo apt install -y docker.io curl git
sudo usermod -a -G docker ubuntu
  1. Add any authorized keys for people that need to connect with ssh
  2. For the web server run this (needed to auto generate SSL certificates using LetsEncrypt)
mkdir -p /home/ubuntu/letsencrypt && touch /home/ubuntu/letsencrypt/acme.json && chmod 600 /home/ubuntu/letsencrypt/acme.json
  1. Enable HTTPS (443) incoming traffic in web instance
  2. Enable ports 5432 for incoming traffic in DB instance
  3. Run kamal setup

For normal deploys run kamal deploy.
If env vars change you will have to push them with kamal env push

@santiagorodriguez96 santiagorodriguez96 force-pushed the sr--setup-kamal branch 2 times, most recently from 68bc0b8 to 5756295 Compare April 5, 2024 14:50
@santiagorodriguez96
infra: add TLS support through Let's Encrypt using Traefik
0ff0cc8
@santiagorodriguez96
infra: configure traefik to redirect from http to https
8a50535
@santiagorodriguez96
infra: enable traefik access logs
5fe6d91
@santiagorodriguez96
build: force SSL again
7118a90
@santiagorodriguez96
infra: set up kamal db accessory
581394f
@santiagorodriguez96
chore: clean up sample hooks
6fae6ff
@santiagorodriguez96
infra: set memory limit for server's app docker container
b71935b 
To prevent the docker container from using too much memory from the
server, we are adding a memory limit.

By adding a memory limit, docker will kill the container when it gets to
the limit of memory usage and the docker container will be restarted – as
its started up with the `--restart unless-stopped` option.

However, we need to add the logic for cleaning the `server.pid` if
exists when starting the server given that when the docker container
starts itself after being killed it runs into an error when starting the
server as the `server.pid` already exists:

```
a server is already running (pid: 1, file: /rails/tmp/pids/server.pid)
```
@santiagorodriguez96 santiagorodriguez96 merged commit 7e27aa7 into master Aug 23, 2024
1 check passed
@santiagorodriguez96 santiagorodriguez96 deleted the sr--setup-kamal branch August 23, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@santiagorodriguez96