Skip to content
RAMP Documentation

Docker Full

RAMP Full is a single-server production deployment designed for small to medium teams (10—100 users). It uses PostgreSQL for data storage and includes an LDAP server for enterprise authentication.

Best for

  • Production environments (10—100 users)
  • Enterprise authentication with LDAP
  • Single-server deployments
  • Teams that do not need high availability

Limitations

  • Single point of failure (no redundancy)
  • No horizontal scaling
  • Files stored locally (not shared storage)
  • Downtime during updates and restarts

Prerequisites

Section titled “Prerequisites”
  • Docker Desktop 4.0+ or Docker Engine 20.10+
  • Docker Compose 2.0+
  • Available RAM: 4 GB minimum (8 GB recommended)
  • Disk Space: 10 GB minimum

Quick start

Section titled “Quick start”

  1. Navigate to the RAMP directory:

    Terminal window
    cd /path/to/RAMP

  2. Create a .env file with custom passwords:

    Terminal window
    DB_PASSWORD=YourSecureDbPassword123!
    LDAP_ADMIN_PASSWORD=YourLdapAdminPassword123!
    LDAP_JWT_SECRET=your_jwt_secret_minimum_32_characters_long!
    JWT_SECRET=YourApiJwtSecretAtLeast32CharsLong!

  3. Start RAMP Full:

    Terminal window
    docker-compose -f docker-compose.full.yml up -d --build

    This downloads PostgreSQL, LDAP, and Nginx images, builds the RAMP images, creates the database, runs migrations, and starts all services.

  4. Monitor startup (wait for all services to show “healthy” — typically 2—3 minutes):

    Terminal window
    docker-compose -f docker-compose.full.yml ps

  5. Open your browser at http://localhost.

Default credentials

Section titled “Default credentials”

RAMP admin

Section titled “RAMP admin”
FieldValue
Emailadmin@ramp.local
PasswordAdmin123!

PostgreSQL

Section titled “PostgreSQL”
FieldValue
Hostlocalhost
Port5432
Databaseramp
Usernameramp
PasswordRampDbPassword123! (or from .env)

Connection string: postgresql://ramp:RampDbPassword123!@localhost:5432/ramp

LDAP admin panel

Section titled “LDAP admin panel”
FieldValue
URLhttp://localhost:17170
Usernameadmin
PasswordLdapAdmin123! (or from .env)

LDAP connection info:

FieldValue
Hostlocalhost (or ramp-ldap from containers)
Port3890
Base DNdc=ramp,dc=local
Bind DNuid=admin,ou=people,dc=ramp,dc=local

Service URLs

Section titled “Service URLs”
ServiceURLDescription
Web Applicationhttp://localhostMain RAMP interface
API (via Nginx)http://localhost/apiAPI endpoints through reverse proxy
API (direct)http://localhost:5000Direct API access
LDAP Adminhttp://localhost:17170LDAP user management
PostgreSQLlocalhost:5432Database access

Data persistence

Section titled “Data persistence”

All data is stored in Docker volumes:

Terminal window
docker volume ls | grep ramp
# ramp-full-db        (PostgreSQL data)
# ramp-full-ldap      (LDAP users & groups)
# ramp-full-data      (Application data)
# ramp-full-logs      (Application logs)
# ramp-full-uploads   (File attachments)

LDAP user management

Section titled “LDAP user management”

Add LDAP users

Section titled “Add LDAP users”
  1. Open the LDAP admin panel at http://localhost:17170.
  2. Log in as admin.
  3. Navigate to Users then Create User.
  4. Fill in username (email format recommended), display name, password, and email.
  5. Click Create.
  6. Optionally, add the user to groups under the Groups tab.

Sync LDAP users to RAMP

Section titled “Sync LDAP users to RAMP”
  1. Log in to RAMP as administrator.
  2. Navigate to Admin then Users.
  3. Click Sync LDAP Users.
  4. LDAP users appear in RAMP.
  5. Assign RAMP roles to users as needed.

Backup and restore

Section titled “Backup and restore”

PostgreSQL

Section titled “PostgreSQL”
Terminal window
mkdir -p ./backups


# Plain SQL backup
docker exec ramp-db pg_dump -U ramp -d ramp > ./backups/ramp_$(date +%Y%m%d).sql


# Compressed backup
docker exec ramp-db pg_dump -U ramp -d ramp | gzip > ./backups/ramp_$(date +%Y%m%d).sql.gz

LDAP users

Section titled “LDAP users”
Terminal window
docker exec ramp-ldap /app/lldap export > ./backups/ldap_$(date +%Y%m%d).ldif

File uploads

Section titled “File uploads”
Terminal window
docker cp ramp-api:/app/uploads ./backups/uploads_$(date +%Y%m%d)

Common operations

Section titled “Common operations”

View logs

Section titled “View logs”
Terminal window
# All services
docker-compose -f docker-compose.full.yml logs -f


# Specific service
docker-compose -f docker-compose.full.yml logs -f ramp-api
docker-compose -f docker-compose.full.yml logs -f ramp-db


# Last 50 lines
docker-compose -f docker-compose.full.yml logs --tail=50

Restart services

Section titled “Restart services”
Terminal window
# Restart all
docker-compose -f docker-compose.full.yml restart


# Restart specific service
docker-compose -f docker-compose.full.yml restart ramp-api

Stop services

Section titled “Stop services”
Terminal window
docker-compose -f docker-compose.full.yml stop

Update to latest version

Section titled “Update to latest version”
Terminal window
git pull
docker-compose -f docker-compose.full.yml build
docker-compose -f docker-compose.full.yml up -d

Troubleshooting

Section titled “Troubleshooting”

Cannot access http://localhost

Section titled “Cannot access http://localhost”
Terminal window
# Check container status -- all should show "Up (healthy)"
docker-compose -f docker-compose.full.yml ps


# Check logs for errors
docker-compose -f docker-compose.full.yml logs

LDAP authentication not working

Section titled “LDAP authentication not working”
Terminal window
# Verify LDAP server is running
docker-compose -f docker-compose.full.yml ps ramp-ldap


# Test LDAP connection
docker exec ramp-ldap /app/lldap healthcheck

Then verify users exist in the LDAP admin panel at http://localhost:17170 under ou=people,dc=ramp,dc=local.

Database connection errors

Section titled “Database connection errors”
Terminal window
# Check PostgreSQL health
docker exec ramp-db pg_isready -U ramp
# Expected: "ramp-db:5432 - accepting connections"


# Verify database exists
docker exec ramp-db psql -U ramp -l
# Should list "ramp" database


# Restart database then API
docker-compose -f docker-compose.full.yml restart ramp-db
# Wait 10 seconds
docker-compose -f docker-compose.full.yml restart ramp-api

High memory usage

Section titled “High memory usage”
Terminal window
docker stats

Expected memory usage:

ServiceRAM
PostgreSQL200—500 MB
LDAP50—100 MB
API500 MB — 1 GB
Web50 MB
Nginx10—20 MB
Total~1—2 GB

If usage is significantly higher, restart the services:

Terminal window
docker-compose -f docker-compose.full.yml restart

Performance tuning

Section titled “Performance tuning”

PostgreSQL memory

Section titled “PostgreSQL memory”

Edit docker-compose.full.yml:

ramp-db:
  environment:
    - POSTGRES_SHARED_BUFFERS=256MB
    - POSTGRES_EFFECTIVE_CACHE_SIZE=1GB

API memory limit

Section titled “API memory limit”
ramp-api:
  deploy:
    resources:
      limits:
        memory: 2G

Connection pooling

Section titled “Connection pooling”
ramp-api:
  environment:
    - Database__MaxPoolSize=100
    - Database__MinPoolSize=10

Restart the affected services after making changes:

Terminal window
docker-compose -f docker-compose.full.yml restart ramp-db ramp-api

Monitoring

Section titled “Monitoring”
Terminal window
# Application health
curl http://localhost/_health


# Database size
docker exec ramp-db psql -U ramp -d ramp -c "SELECT pg_size_pretty(pg_database_size('ramp'));"


# Active database connections
docker exec ramp-db psql -U ramp -d ramp -c "SELECT count(*) FROM pg_stat_activity;"

Security best practices

Section titled “Security best practices”

  1. Change all default passwords — RAMP admin, PostgreSQL, LDAP, and JWT secret. Set them in the .env file and restart.

  2. Enable HTTPS — mount SSL certificates into the Nginx container or place an external reverse proxy in front:

    ramp-web:
      volumes:
        - ./ssl/cert.pem:/etc/nginx/cert.pem
        - ./ssl/key.pem:/etc/nginx/key.pem

  3. Restrict database access — remove the external port binding for PostgreSQL in docker-compose.full.yml:

    ramp-db:
      ports:
        # Comment out to prevent external access
        # - "5432:5432"

  4. Set up automated backups — create a cron job:

    backup.sh
    #!/bin/bash
    DATE=$(date +%Y%m%d_%H%M%S)
    docker exec ramp-db pg_dump -U ramp -d ramp | gzip > /backups/ramp_${DATE}.sql.gz
    

    # Add to crontab (daily at 2 AM)
    # 0 2 * * * /path/to/backup.sh

Resource requirements

Section titled “Resource requirements”
MinimumRecommended
RAM4 GB8 GB
CPU2 cores4 cores
Disk10 GB50 GB (depends on uploads)

When to upgrade

Section titled “When to upgrade”

Consider upgrading from Full to Docker Cluster if you need:

  • High availability (zero downtime during updates)
  • Horizontal scaling (multiple API instances)
  • Load balancing
  • Centralized file storage (MinIO/S3)
  • Redis caching and real-time messaging across instances

Migration path

Section titled “Migration path”
  1. Backup the PostgreSQL database.
  2. Deploy the Cluster setup.
  3. Import the database into the Cluster PostgreSQL instance.
  4. Configure shared file storage (MinIO).
  5. Test and switch over.
Section titled “Related topics”
Docker Lite Minimal Docker deployment with SQLite for evaluation and small teams
Docker Cluster Multi-node high-availability deployment with load balancing, Redis, and MinIO
Application Settings Reference Complete reference for RAMP's appsettings.json configuration