Skip to main content

Documentation 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 ships as two Docker images — julioreynadev/autolog-api and julioreynadev/autolog-web — ready to run on any Docker host. No secrets are baked into either image; all sensitive values are injected at container startup through environment variables, making the images safe to share publicly and straightforward to configure per environment.

​
Quick Start

1

Pull the pre-built images

Pull both official images from Docker Hub:
docker pull julioreynadev/autolog-api:latest
docker pull julioreynadev/autolog-web:latest
2

Run the API container

Start the backend API, supplying your database connection string, CORS origin, and JWT secret as environment variables:
docker run -d \
  --name autolog-api \
  --restart unless-stopped \
  -p 5030:8080 \
  -e "ConnectionStrings__DefaultConnection=Host=host.docker.internal;Database=YOUR_DB;Username=YOUR_USER;Password=YOUR_PASS" \
  -e "Cors__AllowedOrigins__0=https://frontend.yourdomain.com" \
  -e "JwtSettings__Secret=YOUR_VERY_LONG_SECRET_KEY" \
  julioreynadev/autolog-api:latest
3

Run the web container

Start the frontend, pointing it at your running API:
docker run -d \
  --name autolog-web \
  --restart unless-stopped \
  -p 5020:80 \
  -e "API_URL=https://api.yourdomain.com/api" \
  julioreynadev/autolog-web:latest
4

Access the application

Open your browser and navigate to http://your-host:5020. The Angular frontend will load and communicate with the API on port 5030.
No hardcoded secrets exist anywhere in the AutoLog repository. Every sensitive value — database credentials, JWT signing keys, CORS origins — is injected at runtime via environment variables. The Docker images are safe to pull and share publicly.

​
Port Reference

ServiceInternal Container PortHost-Exposed Port
autolog-api (ASP.NET Core)80805030
autolog-web (Nginx)805020

​
Building from Source

If you have forked the repository and want to build and push your own images, use Docker Buildx for cross-platform AMD64 builds. This ensures the images run correctly on Linux AMD64 production servers regardless of whether you build on Apple Silicon or another architecture.
1

Build and push the frontend image

Run this command from the repository root:
docker buildx build --platform linux/amd64 \
  -t docker_username/autolog-web:v1.0.0 \
  -t docker_username/autolog-web:latest \
  --push ./frontend
The frontend Dockerfile performs a two-stage build: Node 22 Alpine compiles the Angular 20 app in production mode, then the compiled output is copied into an nginx:alpine image alongside the custom nginx.conf and the entrypoint.sh runtime script.
2

Build and push the backend image

docker buildx build --platform linux/amd64 \
  -t docker_username/autolog-api:v1.0.0 \
  -t docker_username/autolog-api:latest \
  --push ./backend/src
The backend Dockerfile uses a three-stage build: the .NET 10 SDK image restores and compiles the solution in Release mode, publishes the output, then copies it into the lean mcr.microsoft.com/dotnet/aspnet:10.0 runtime image. The final image exposes port 8080, which is the default ASP.NET Core port in .NET 8+ containers.

Build docs developers (and LLMs) love

Get started for freeTalk to us