astra-community/
├── src/
├── commands/
├── events/
├── utils/
├── config.example.yml
├── package.json
├── index.js
├── setup.sh
└── README.md

# Using SCP
scp -r astra-community/ user@hostname:/path/to/bot/directory/

# Using rsync
rsync -avz --exclude='node_modules' astra-community/ user@hostname:/path/to/bot/

# Discord Bot Configuration
# Your Discord bot token (from Discord Developer Portal)
token: "YOUR_BOT_TOKEN"

# Your Discord application/client ID (from Discord Developer Portal)
clientId: "YOUR_BOT_CLIENT_ID"

# Your Discord user ID (for owner-only commands)
ownerId: "YOUR_DISCORD_USER_ID"

# Your license key for bot validation
licenseKey: "YOUR_LICENSE_KEY"

# Additional settings
bot:
  # Bot status and activity
  status: "online"  # online, idle, dnd, invisible
  activity:
    type: "WATCHING"  # PLAYING, STREAMING, LISTENING, WATCHING
    name: "the community"

# Command settings
commands:
  # Global command deployment (set to false for guild-only testing)
  global: true
  
  # Guild ID for testing (only used if global is false)
  testGuildId: "YOUR_TEST_GUILD_ID"

# If you have shell access
npm install --only=production

# If using hosting provider's interface
# Look for "Install Dependencies" or "NPM Install" button

# Extract the files
unzip astra-community-v1.1.zip
cd astra-community

# Verify all files are present
ls -la

# Check package.json for correct version
cat package.json | grep version

# Verify setup script permissions
ls -l setup.sh

# Clean any existing node_modules
rm -rf node_modules package-lock.json

# Install production dependencies only
npm install --only=production

# Or install all dependencies (including development tools)
npm install

# Verify installation success
npm list --depth=0

# Check for vulnerabilities
npm audit

# Fix any vulnerabilities
npm audit fix

# Using Yarn
yarn install --production

# Using pnpm (faster alternative)
pnpm install --prod

# Copy the example configuration
cp config.example.yml config.yml

# Create backup of example
cp config.example.yml config.example.yml.backup

# Edit with your preferred editor
nano config.yml

# Discord Bot Configuration
# Your Discord bot token (from Discord Developer Portal)
token: "YOUR_BOT_TOKEN"

# Your Discord application/client ID (from Discord Developer Portal)
clientId: "YOUR_BOT_CLIENT_ID"

# Your Discord user ID (for owner-only commands)
ownerId: "YOUR_DISCORD_USER_ID"

# Your license key for bot validation
licenseKey: "YOUR_LICENSE_KEY"

# Additional settings
bot:
  # Bot status and activity
  status: "online"  # online, idle, dnd, invisible
  activity:
    type: "WATCHING"  # PLAYING, STREAMING, LISTENING, WATCHING
    name: "the community"

# Command settings
commands:
  # Global command deployment (set to false for guild-only testing)
  global: true
  
  # Guild ID for testing (only used if global is false)
  testGuildId: "YOUR_TEST_GUILD_ID"

# Create .env file for local development
touch .env
chmod 600 .env  # Restrict permissions

# Add sensitive configuration to .env
cat << EOF > .env
# Discord Configuration
DISCORD_TOKEN=your_actual_bot_token_here
DISCORD_CLIENT_ID=your_actual_client_id_here
DISCORD_OWNER_ID=your_actual_user_id_here

# License Configuration
LICENSE_KEY=your_actual_license_key_here

# Environment
NODE_ENV=production
EOF

# Reference environment variables in config.yml
token: ${DISCORD_TOKEN}
clientId: ${DISCORD_CLIENT_ID}
ownerId: ${DISCORD_OWNER_ID}
licenseKey: ${LICENSE_KEY}

# Set system environment variables
export DISCORD_TOKEN="your_token_here"
export LICENSE_KEY="your_license_here"

# Or add to system profile
echo 'export DISCORD_TOKEN="your_token_here"' >> ~/.bashrc
source ~/.bashrc

# Create data directory for SQLite database
mkdir -p data logs

# Set proper permissions
chmod 755 data logs
chmod 700 data  # Restrict database directory access

# SQLite database will be created automatically on first run
# The database file will be: data/astra.db

# Standard production start
npm start

# Development mode with auto-restart on file changes
npm run dev

# Debug mode with verbose logging
npm run debug

# Production mode with PM2 process manager
npm run production

# Custom start with specific Node.js options
node --max-old-space-size=1024 index.js

# Start with environment file
NODE_ENV=production node index.js

# Start with custom config file
CONFIG_FILE=./config.production.yml npm start

# Create PM2 ecosystem file
cat << EOF > ecosystem.config.js
module.exports = {
  apps: [{
    name: 'astra-community',
    script: 'index.js',
    instances: 1,
    autorestart: true,
    watch: false,
    max_memory_restart: '512M',
    env: {
      NODE_ENV: 'production'
    },
    error_file: './logs/pm2-error.log',
    out_file: './logs/pm2-out.log',
    log_file: './logs/pm2-combined.log',
    time: true
  }]
};
EOF

# Start with ecosystem file
pm2 start ecosystem.config.js