SkyPort is designed to run on real VPS infrastructure with your own domain, HTTPS, reverse proxy, and persistent background services.

This guide explains how to deploy SkyPort securely in production using:

• Caddy
• Nginx
• Apache
• Cloudflare DNS
• systemd services
• Reverse proxy workflows

The setup is intentionally lightweight and optimized for low-end VPS environments.

Install From Scratch

The production installer downloads the release binaries, writes the environment file, and installs the service for the platform.

To install from scratch on a Linux VPS, open a root shell first and then run the installer:

sudo su
curl -fsSL https://skyport.akashhalder.in/installer.sh | bash

If you want to inspect the script first, download it to a file and review it before running it:

sudo su
curl -fsSL https://skyport.akashhalder.in/installer.sh -o installer.sh
less installer.sh
bash installer.sh

The installer does the following:

• installs skyport-server and the skyport CLI under /usr/local/bin
• creates /opt/skyport, /etc/skyport, and the application data directories
• writes the production environment file with ALLOWED_ORIGINS=*
• installs and starts the native service manager for the platform

Recommended Production Architecture

Internet
│
├── Domain (skyport-vps.example.com)
│
├── DNS Provider
│   └── A Record -> VPS IP
│
├── Reverse Proxy
│   ├── Caddy (Recommended)
│   ├── Nginx
│   └── Apache
│
├── HTTPS / SSL
│
└── SkyPort Backend (localhost:8080)
    ├── Web UI
    ├── API
    ├── Docker Integration
    ├── PM2 Integration
    └── Metrics

Important Production Notes

skyport start
skyport start server
skyport start webui

Requirements

Before starting, make sure you have:

• A Linux VPS
• At least 1 vCPU and 512 MB RAM
• 2 GB RAM recommended for Docker workloads
• A public server IP
• A domain or subdomain
• ports 80 and 443 open
• SkyPort installed

Type: A
Name: skyport-vps
Value: YOUR_SERVER_IP
TTL: Auto

skyport-vps.example.com

ping skyport-vps.example.com

which skyport-server

/usr/local/bin/skyport-server

/usr/local/bin/skyport-server

SKYPORT ready
➜ Local: http://localhost:8080

CTRL + C

Running SkyPort As A Service

For production environments, SkyPort should run as the installed native service.

This ensures:

• automatic startup after reboot
• crash recovery
• persistent background execution
• centralized logging
• proper Linux or macOS process management

The supported service commands are:

skyport service install
skyport service start
skyport service status
skyport service restart
skyport service stop
skyport service enable
skyport service disable
skyport service uninstall

skyport start is still available in the CLI, but it is for local or foreground usage. For production, use the service commands above.

sudo nano /etc/systemd/system/skyport.service

[Unit]
Description=SkyPort Backend
After=network.target

[Service]
Type=simple

ExecStart=/usr/local/bin/skyport-server
WorkingDirectory=/opt/skyport

User=skyport
Group=skyport

Restart=always
RestartSec=3

StandardOutput=journal
StandardError=journal

Environment=SKYPORT_ENV=production
Environment=SKYPORT_PORT=8080

[Install]
WantedBy=multi-user.target

sudo mkdir -p /opt/skyport

sudo systemctl daemon-reload

sudo systemctl enable skyport

sudo systemctl start skyport

sudo systemctl status skyport

sudo journalctl -u skyport -f

curl http://127.0.0.1:8080/api/v1/health

{
  "service": "skyport",
  "status": "ok"
}

Recommended Reverse Proxy: Caddy

SkyPort works best with Caddy because:

• automatic HTTPS
• automatic SSL renewal
• simple configuration
• lightweight resource usage
• HTTP/2 support
• minimal maintenance

Install Caddy

sudo apt update
sudo apt install -y caddy

sudo nano /etc/caddy/Caddyfile

skyport-vps.example.com {

    reverse_proxy localhost:8080

    encode gzip

    header {
        Strict-Transport-Security "max-age=31536000;"
        X-Content-Type-Options "nosniff"
        X-Frame-Options "DENY"
        Referrer-Policy "strict-origin-when-cross-origin"
    }
}

sudo systemctl restart caddy

sudo systemctl status caddy

https://skyport-vps.example.com

Nginx Setup

If you prefer Nginx:

sudo apt install -y nginx

sudo nano /etc/nginx/sites-available/skyport

server {
    listen 80;

    server_name skyport-vps.example.com;

    location / {
        proxy_pass http://localhost:8080;

        proxy_http_version 1.1;

        proxy_set_header Host $host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

sudo ln -s /etc/nginx/sites-available/skyport /etc/nginx/sites-enabled/

sudo nginx -t

sudo systemctl restart nginx

sudo apt install certbot python3-certbot-nginx

sudo certbot --nginx -d skyport-vps.example.com

Apache Setup

If your server already uses Apache:

sudo apt install apache2

sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod rewrite
sudo a2enmod headers

sudo nano /etc/apache2/sites-available/skyport.conf

<VirtualHost *:80>

    ServerName skyport-vps.example.com

    ProxyPreserveHost On

    ProxyPass / http://localhost:8080/
    ProxyPassReverse / http://localhost:8080/

    RequestHeader set X-Forwarded-Proto "http"

</VirtualHost>

sudo a2ensite skyport.conf

sudo systemctl restart apache2

Environment Variables

Example production configuration:

SKYPORT_HOST=0.0.0.0
SKYPORT_PORT=8080

SKYPORT_DB_PATH=./data/skyport.db
SKYPORT_WORKSPACE_ROOT=./workspace

JWT_SECRET=change-this-secret
SKYPORT_ENCRYPTION_KEY=base64-key

ENABLE_METRICS=true
ENABLE_DOCKER=true
ENABLE_PM2=true

Firewall Configuration

sudo ufw allow 80
sudo ufw allow 443

sudo ufw enable

Production Checklist

• Domain points to VPS IP
• SkyPort service running
• Reverse proxy configured
• HTTPS enabled
• Firewall configured
• Environment variables secured
• Docker permissions verified
• PM2 access verified
• systemd service enabled

Troubleshooting

Port Already In Use

Check active processes:

sudo lsof -i :8080

Verify Backend Health

curl http://127.0.0.1:8080/api/v1/health

Reverse Proxy Cannot Connect

Verify backend status:

sudo systemctl status skyport

Service Logs

sudo journalctl -u skyport -f

HTTPS Not Working

Verify:

• DNS propagation completed
• ports 80/443 are open
• reverse proxy is running
• SSL certificate generation succeeded

Uninstall SkyPort

If you need to remove SkyPort from a machine, use the hosted uninstaller:

curl -fsSL https://skyport.akashhalder.in/uninstaller.sh | sudo bash

This hosted script removes:

• skyport-server
• skyport CLI
• the Linux systemd service or macOS launchd service
• the environment file and service configuration

It also stops any running skyport-server process before deleting files, so the API should not keep serving after uninstall.

By default, the uninstaller keeps the data directory so you can reinstall later without losing state.

To remove the data directory as well:

curl -fsSL https://skyport.akashhalder.in/uninstaller.sh -o uninstall.sh
sudo SKYPORT_PURGE_DATA=1 bash uninstall.sh

Recommended Production Stack

Next Steps

• Security
• Scaling
• Environment Variables
• CLI Reference
• Docker Integration
• systemd Documentation