Vultr Deployment

This guide will walk you through the process of deploying and configuring DBConvert Streams on Vultr.

Deployment Options

DBConvert Streams can be deployed on Vultr in two ways:

1. Vultr Marketplace One-Click App (recommended for quick setup)
2. Manual Installation on a Vultr instance

Option 1: Deploying from Vultr Marketplace

Step 1: Deploy from Marketplace

1. Log in to your Vultr account
2. Visit DBConvert Streams on Vultr Marketplace
3. Click "Deploy" button
4. Choose your deployment options:
   • Select server location
   • Choose server size (minimum 2GB RAM recommended)
   • Configure additional options as needed
5. Complete the deployment process

Step 2: Access Your Instance

1. Wait for the deployment to complete (~5-10 minutes)
2. Note your server's IP address from the Vultr dashboard
3. Connect to your server via SSH:

   ssh root@YOUR_SERVER_IP

Step 3: Access the Application

Once deployed, you can access DBConvert Streams at:

• Web UI: http://YOUR_SERVER_IP
• API: http://YOUR_SERVER_IP/api/

Option 2: Manual Installation

Prerequisites

• Vultr account
• SSH client for server access

Step 1: Deploy a Cloud Instance

1. Log in to Vultr Control Panel
2. Click "Deploy Server" or the "+" button
3. Choose Server:
   • Select any supported Linux distribution
   • Choose instance type (2GB RAM minimum recommended)
   • Select preferred datacenter region
4. Configure Authentication:
   • Choose SSH key authentication (recommended)
   • Add your SSH public key or generate a new one
5. Configure Firewall:
   • Create a new firewall group
   • Allow SSH traffic (port 22)
   • Allow HTTPS traffic (port 443)
   • Allow HTTP traffic (port 80)
6. Add any additional options as needed
7. Click "Deploy Now"

Step 2: Connect to Your Instance

# Connect using SSH
ssh root@YOUR_INSTANCE_IP

Step 3: Install and Start DBConvert Streams

# Install DBConvert Streams
curl -fsSL https://dbconvert.nyc3.digitaloceanspaces.com/downloads/streams/latest/docker-install.sh | sh

# Start with HTTP
./start.sh

# Or start with HTTPS (recommended for production)
./start.sh -s

Managing Services

Stop Services

./stop.sh

Update Services

./update.sh