https://github.com/loldruger/nginx-docker-ssl-template

This template runs on Rust axum as backend with nginx, postgres and redis over automatical SSL setup!
https://github.com/loldruger/nginx-docker-ssl-template

backend docker letsencrypt ngnix postgres redis reverse-proxy rust sqlx ssl template tokio

Last synced: 2 months ago
JSON representation

This template runs on Rust axum as backend with nginx, postgres and redis over automatical SSL setup!

• Host: GitHub
• URL: https://github.com/loldruger/nginx-docker-ssl-template
• Owner: loldruger
• Created: 2023-03-24T18:40:13.000Z (almost 2 years ago)
• Default Branch: master
• Last Pushed: 2024-07-26T19:23:35.000Z (6 months ago)
• Last Synced: 2024-07-27T18:53:34.607Z (6 months ago)
• Topics: backend, docker, letsencrypt, ngnix, postgres, redis, reverse-proxy, rust, sqlx, ssl, template, tokio
• Language: Shell
• Homepage:
• Size: 47.9 KB
• Stars: 5
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Introduction

this template runs on `tokio`, `sqlx`, `axum` in `Rust programming language` with `nginx`, `postgres` and `redis`, over `Let's Encrypt SSL`

you can easily replace backend system, currently running on Rust axum, with whatever you want!

# Getting Started

## Prerequisite

 1. You need to setup DNS config

 2. Set .env file to yours

.env:

```python

#certbot

STAGING="true" #if you are testing, keep it true

EMAIL="[email protected]"

DOMAINS="project-1.com" #project-1.com project-2.com...

#postgres && pg-admin

POSTGRES_DATABASE="example_db"

POSTGRES_PASSWORD="example_password"

PGADMIN_DEFAULT_EMAIL="[email protected]"

PGADMIN_DEFAULT_PASSWORD="example_password"

```

 3. Generate nginx configuration template files for each `DOMAINS` by executing

 ```

 $ sh init.sh

 ```

Which yields `domain.conf.template` files into `/data/etc/nginx/conf.d`

 4. Modify the nginx configuration template files to what you need. And rename them without the `.template` extension.

and finally, Enter this command:

```

$ sh deploy.sh

```

on your terminal. it will be all automatically set up. And it now supports multiple domains certification!

if you get successful result but cannot access through your domain,  `$ docker compose restart nginx` to reload `nginx service`

# TroubleShooting

 1. If you get an error at certbot phase, like `Certbot failed to authenticate some domains... Fetching  Connection refused`, Check if the file `/data/etc/letsencrypt/ssl-dhparams.pem` is 0 Bytes.

if so, clean up your docker network and data files, then follow the second step of fitting MTU length.

 2. If you get troubles on internet connection in container, uncomment network set up bottom of the `docker-compose.yaml` file to fit the MTU length 1450 or else.