AutoLog uses Nginx at two distinct layers. TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/JReyna217/AutoLog/llms.txt
Use this file to discover all available pages before exploring further.
autolog-web Docker container bundles its own Nginx instance to serve the compiled Angular SPA and handle client-side routing. On top of that, an outer Nginx process running directly on the Ubuntu host acts as a reverse proxy: it terminates SSL, redirects HTTP traffic to HTTPS, and forwards requests to the appropriate Docker container ports. This separation means the inner Nginx handles application concerns while the outer Nginx handles infrastructure concerns.
Prerequisites
- Ubuntu Server with Nginx installed (
sudo apt install nginx) - A domain name pointed at your server’s public IP
- An SSL certificate and private key available on the server (see the Certbot tip below for a free option)
- AutoLog containers already running (see the Docker deployment guide)
Configuring the Reverse Proxy
Create the site configuration file
Create a new Nginx server block at Paste in the following configuration, replacing the placeholders with your actual domain name and certificate paths:
/etc/nginx/sites-available/autolog:Test the configuration
Validate the Nginx configuration before reloading to catch any syntax errors:A successful test will output
syntax is ok and test is successful.Remember to replace the following placeholders in the configuration above before saving:
autolog.yourdomain.com— your actual domain name (must match your DNS record)/etc/nginx/ssl/your_cert.crt— the absolute path to your SSL certificate file/etc/nginx/ssl/your_key.key— the absolute path to your SSL private key file5020— the host port yourautolog-webcontainer is bound to (default from the Docker guide)
Internal Container Nginx
Theautolog-web container ships with its own nginx.conf that handles Angular SPA routing and static asset caching. The key directive is try_files $uri $uri/ /index.html, which ensures that direct navigation to any Angular route (e.g., /fuel-logs/123) returns index.html instead of a 404 — letting the Angular Router handle the URL client-side.
/etc/nginx/conf.d/default.conf). You do not need to modify it unless you are building a custom frontend image.