# HelioHost shared-hosting deployment

This package is prepared for HelioHost shared hosting using the documented Bash-CGI Discord-bot control approach.

## Layout

Upload the project as:

`/httpdocs/discord-bot/`

Upload `bot_control/` as:

`/httpdocs/bot_control/`

The bot controller is intentionally separate from the Node.js Passenger application model because Passenger stops inactive Node applications, which is unsuitable for a Discord Gateway connection.

## Install dependencies

Use Plesk's Node.js tools for the `/httpdocs/discord-bot` application root and run **NPM Install**. Do not put the Discord token in `setup.txt` or source code.

Create `.env` in the bot directory with:

`DISCORD_TOKEN=your_bot_token`

If Plesk's Node.js manager is enabled temporarily for dependency installation/testing, disable it before using the Bash-CGI controller so Passenger does not also launch a second bot process.

## Start

Open:

`https://YOUR-DOMAIN/bot_control/`

Then select **Start**.

The controller writes output to `bot_control/discord-server-blueprint.log`.

## Stop

Use **Stop** from the same page. If a stale process remains, use Plesk > Websites & Domains > your domain > Node.js > Disable Node.js if Passenger is involved, or contact HelioHost support rather than repeatedly spawning processes.

## Important

HelioHost shared hosting has resource limits. Monitor account load and avoid multiple copies of the bot running simultaneously.