Configuration Setup of .env and Database



After the server restarts, you need to configure the .env file and gain access to the database to ensure the bot operates correctly.

📝 Preparing the .env Configuration File #

The .env file contains all important parameters the bot uses to connect to external services and the database. Filling it out correctly is key to stable operation.

1. 1. Connect to the server via SSH (if not already connected):

      ssh root@SERVER_IP_ADDRESS

      Replace SERVER_IP_ADDRESS with your actual server IP.

   2. Navigate to the bot directory:

      cd /MYBOTS/DEXBOT/

      Make sure you are in the bot folder — it should contain all necessary scripts.

   3. Find the config template and create the working .env file:

      mv .env.template .env

      This creates the .env file from the template, which you need to fill in.

   4. Open .env in any text editor, for example nano or vim:

      nano .env

   5. Fill in all the required fields:
      • License Key: Your personal DEXBOT key to activate the bot.
      • OKX API: Enter the API Key, Secret, and Passphrase for OKX services.
      • Wallets: Addresses for Solana and EVM blockchains (e.g., Ethereum, Binance Smart Chain, etc.).
      • Telegram Token and Admin ID: Your Telegram bot token and administrator ID for managing the bot.
      • Database settings: Host, port, username, password, and database name you specified earlier during installation.

After filling in, save the file and exit the editor (in nano: Ctrl+O → Enter → Ctrl+X).

1. Important: be careful entering data — configuration errors may cause failures.

🔐 Accessing the Database via Adminer Web Interface #

After successful installation and server reboot, the database is ready to use. For easy management, use the Adminer web interface.

1. Open your browser and go to:

   http://SERVER_IP_ADDRESS

   Replace SERVER_IP_ADDRESS with your server’s IP address.

2. You will see the Adminer login page — a simple and lightweight database management tool.
3. Enter the admin username and password you set during installation.
4. After login, you can browse tables, make backups, run queries, and monitor database operations.

🔧 Security and Maintenance Recommendations #

• Never share or expose the .env file to third parties — it contains confidential data.
• Regularly back up your database, especially before major changes.
• If you modify the .env file, restart the bot afterward to apply the new settings.
• Use Adminer only from a secure network to prevent unauthorized access.
• Keep your server and database software updated to protect against vulnerabilities.