sudo mkdir -p /var/www/1pogolinks sudo chown $USER:$USER /var/www/1pogolinks cd /var/www/1pogolinks git clone https://github.com/1pogo/1pogolinks.git . Log into your PostgreSQL instance:
> 1pogolinks@1.4.2 start > node server.js Server listening on port 3000 Open a browser and visit http://your-server-ip:3000 . If the login page loads, your is functioning. Chapter 4: Production-Ready Setup – Reverse Proxy with Nginx Running 1pogolinks on port 3000 is fine for testing, but for production you want Nginx in front of it. This section completes a robust 1pogolinks install for live use. Install Nginx: sudo apt install nginx -y Create a new Nginx site configuration: sudo nano /etc/nginx/sites-available/1pogolinks Paste: 1pogolinks install
version: '3.8' services: app: image: 1pogo/1pogolinks:latest ports: - "3000:3000" environment: DB_TYPE: postgresql DB_HOST: db DB_PORT: 5432 DB_NAME: 1pogolinks DB_USER: 1pogouser DB_PASSWORD: strongpassword SESSION_SECRET: your-secret-here depends_on: - db db: image: postgres:13 environment: POSTGRES_DB: 1pogolinks POSTGRES_USER: 1pogouser POSTGRES_PASSWORD: strongpassword volumes: - pgdata:/var/lib/postgresql/data volumes: pgdata: Run: Chapter 4: Production-Ready Setup – Reverse Proxy with
npm run migrate:up Cause: 1pogolinks service is not running. Fix: Fix: Start and enable: cd /var/www/1pogolinks git pull
Start and enable:
cd /var/www/1pogolinks git pull origin main npm install --production npm run migrate:up sudo systemctl restart 1pogolinks Always backup the database before an upgrade. You have now completed a full 1pogolinks install – from bare server to a production-ready, HTTPS-secured link management system. Whether you chose the traditional Linux route or the Docker method, you possess a powerful tool for organizing web resources.
ALTER USER '1pogouser'@'localhost' IDENTIFIED WITH mysql_native_password BY 'strongpassword'; FLUSH PRIVILEGES; Cause: Another Node process is hogging the port. Fix: