This section contains the operational deployment and infrastructure guidance used to run the OneLink platform. Most of the detailed pages in this area are inherited from the upstream deployment base and remain relevant for OneLink deployments.

​
Why This Section Exists

Operating the fork yourself gives you:
  • Data Privacy: Keep all customer data on your own servers
  • Customization: Modify the platform to fit your specific needs
  • Product Control: Deploy your own forked product behavior and branding
  • Compliance: Meet specific regulatory requirements
  • Integration: Deep integration with your existing infrastructure

​
Deployment Options

OneLink currently supports the same broad deployment paths as the inherited deployment base:

​
🐧 Linux VM Deployment

Deploy directly on Ubuntu/Linux virtual machines with our automated installation script.
  • Best for: Traditional server environments
  • Complexity: Low to Medium
  • Maintenance: Manual updates required

​
🐳 Docker Deployment

Use Docker containers for consistent, portable deployments.
  • Best for: Containerized environments
  • Complexity: Medium
  • Maintenance: Easy updates with container pulls

​
☸️ Kubernetes Deployment

Deploy on Kubernetes clusters for enterprise-scale operations.
  • Best for: Large-scale, high-availability deployments
  • Complexity: High
  • Maintenance: Automated with proper CI/CD

​
☁️ Cloud Provider Deployments

One-click deployments on major cloud platforms:
  • AWS: EC2, ECS, and Marketplace options
  • Azure: Container Instances and VM deployments
  • DigitalOcean: Droplets and App Platform
  • Google Cloud: Compute Engine and Cloud Run
  • Heroku: Simple one-click deployment

​
System Requirements

​
Minimum Requirements

  • CPU: 2 cores
  • RAM: 4GB
  • Storage: 20GB SSD
  • OS: Ubuntu 20.04+ or compatible Linux distribution
  • CPU: 4+ cores
  • RAM: 8GB+
  • Storage: 50GB+ SSD
  • Database: PostgreSQL 12+
  • Cache: Redis 6+
  • Reverse Proxy: Nginx or similar

​
What You’ll Need

Before starting a OneLink deployment, ensure you have:

​
Technical Requirements

  • Server or cloud instance meeting minimum requirements
  • Domain name (recommended for production)
  • SSL certificate (Let’s Encrypt recommended)
  • SMTP server for email notifications

​
Access Requirements

  • SSH access to your server
  • Root or sudo privileges
  • Firewall configuration access
  • Object storage (AWS S3, Google Cloud Storage, etc.)
  • CDN for static assets
  • Monitoring tools (APM, logging)
  • Backup solution

​
Security Considerations

When self-hosting the product fork, consider these security aspects:
  • Regular Updates: Keep OneLink and system packages updated
  • Firewall Configuration: Only expose necessary ports
  • SSL/TLS: Always use HTTPS in production
  • Database Security: Secure PostgreSQL with strong passwords
  • Backup Encryption: Encrypt sensitive backup data
  • Access Control: Implement proper user access controls

​
Getting Started

Choose your preferred deployment method:

Quick Start with Docker

Get up and running quickly with Docker containers

Linux VM Installation

Traditional server deployment with our automated script

Kubernetes Deployment

Enterprise-scale deployment on Kubernetes

Cloud Providers

One-click deployments on major cloud platforms

​
Operational Note

Treat this section as the inherited operational base layer. Use the OneLink platform and development docs for product architecture and fork-specific direction.