emailapi | Powerful extensions on top of your mailbox | Email library

Follow the DigitalOcean guide for a one-time initial setup of the instance. Setup nginx by following the guide here. We'll use it as a reverse proxy.
Follow the DigitalOcean guide for a one-time initial setup of the instance. Ensure you setup SSH as the auth/login mechanism
Setup nginx by following the guide here. We'll use it as a reverse proxy.
Serve emailapi application on your domain: cd /etc/nginx/sites-enabled sudo nano emailapi Copy paste the following code block to this file and replace emailapi.io with the domain name that you're using for this application. upstream emailapi_upstream { server 127.0.0.1:3000; keepalive 64; } server { listen 80; listen [::]:80; server_name emailapi.io; location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_pass http://emailapi_upstream/; proxy_redirect off; proxy_read_timeout 240s; } }
Generate a free SSL certificate for your domain (thanks to Let's Encrypt) by using certbot. Follow the guide here. ➡️ Note: certbot will update the nginx file with certificate paths and redirection rules. Here's what the final nginx file for emailapi.io looks like after running certbot. Yours should look similar. upstream emailapi_upstream { server 127.0.0.1:3000; keepalive 64; } server { server_name emailapi.io; location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_pass http://emailapi_upstream/; proxy_redirect off; proxy_read_timeout 240s; } listen [::]:443 ssl; # managed by Certbot listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/emailapi.io/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emailapi.io/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = emailapi.io) { return 301 https://$host$request_uri; } # managed by Certbot listen 80; listen [::]:80; server_name emailapi.io; return 404; # managed by Certbot }
Setup redis using DigitalOcean's Managed Redis in the same region as your DigitalOcean instance and grab the connection string (starts with rediss://). Alternatively, you can install redis locally on your DigitalOcean instance. If you install redis directly on DO instance, you'd need to make sure Docker container can access the port redis is running on on the host machine.
Create environment file on the server. Follow the steps below: Copy content of .env.local file from your local codebase. On remote server, run cd ~/ && mkdir -p apps/emailapi-pipeline && nano .env Paste the copied content in this file, save and exit. Update the REDISCLOUD_URL variable with the connection string from last step.
Visit https://github.com/<your_username>/emailapi/settings/secrets and click on New Secret button. Add the following secrets one by one: DO_HOST = IP address of the DigitalOcean instance DO_USERNAME = Login username of the DigitalOcean instance. GITBUH_USERNAME = Your Github username (typo in key is intentional as Github doesn't allow using GITHUB in secret name) SSH_ID_RSA = Copy paste contents of id_rsa file. This is from the SSH keypair that you'd be using to login to the DigitalOcean instance.
Update .github/workflows/deploy.yml and change aakashlpin with your Github username. Commit this change to your fork's master. This will run a Github Action that'd deploy publish docker container to Github Packages and then pull and run it on the DigitalOcean instance.