Documentation

The Philosophy

Onpush adheres to the Rule of Least Power. We specifically avoid being a "Platform". Platforms impose limits, pricing cliffs, and vendor lock-in.

Onpush does not host your code. Onpush does not run your servers. Onpush simply automates the connection between your GitHub Repository and your Linux VPS using standard, open-source tools: SSH and GitHub Actions.

Key Features

• Zero Config Files: We generate the GitHub Actions workflow for you.
• Secure by Default: SSH Keys are generated per-project and encrypted at rest.
• Push to Deploy: No manual triggers. Just `git push origin main`.
• Instant Feedback: Real-time deployment logs linked directly from your dashboard.

Prerequisites

To use Onpush, you need two things:

1. A GitHub Repository containing your application code.
   Node.js, Python, Go, Rust — anything that runs on Linux.
2. A Linux VPS (Virtual Private Server).
   DigitalOcean, AWS EC2, Hetzner, Linode, or an old laptop in your closet.

Configuring your VPS

Your server needs to be prepared to accept connections. Run these commands on your server:

1. Install Dependencies

Ensure your server has git and your runtime (e.g., Node.js) installed.

# Example for Ubuntu/Debian sudo apt update sudo apt install git nodejs npm

2. Create a Deploy Directory

mkdir -p /var/www/my-app # Ensure your user has permissions sudo chown -R $USER:$USER /var/www/my-app

3. Add the Onpush Key

After you configure a project in Onpush, you will be given a Public Key. You must add this key to your server's authorized_keys file:

# Open the file nano ~/.ssh/authorized_keys # ... Paste the key from Onpush Dashboard ...

Security & Encryption

We take security seriously.

• Private Keys are encrypted using AES-256-CBC before being stored in our database.
• Decryption only happens momentarily during the "Inject" phase to send the key to GitHub.
• GitHub Secrets are used to store the key for the actual deployment. Onpush forgets the raw key immediately after injection.