dhosty

Discord & community · 6 min read

How do you document the accesses and changes to your Discord bot in /Discord-bot-hosting/?

The managed Discord Bot hosting is served in the customer panel. The options offered include start, stop and restart, configurable commands, and welcome and role functions in the respective scope of services. Do not confuse this area with a self-managed VPS. Root access and the administration of your own Linux system are your own requirements; they should not be derived solely from booking a bot package.

Access rights in the Linux container

For the Discord connection, the data of the correct application and the permissions on the desired Discord server are crucial. Keep access keys secret and enter them only in the protected settings provided for it. A bot token is not an OAuth client secret. If a function does not respond, first check the connection, the selected application and the actual assigned permissions instead of distributing additional administrator rights at a flat rate.

Plan the management of the bot as a team task: Who changes commands, who can stop the bot and who takes over a fault? Document these responsibilities separately from the secret access data. A technical deployment does not replace moderation rules for your community. First, test new answers and role actions specifically so that members can understand what a command does and what information becomes visible to the public.

To effectively document accesses and changes, use the panel interface to monitor file changes and configuration files. The isolated Linux environment ensures security without needing additional tools such as PHP or databases – these are available for paid packages.

SFTP and SSH change tracking

The managed Discord Bot hosting is served in the customer panel. The options offered include start, stop and restart, configurable commands, and welcome and role functions in the respective scope of services. Do not confuse this area with a self-managed VPS. Root access and the administration of your own Linux system are your own requirements; they should not be derived solely from booking a bot package.

Important: For free packages, only static HTML, CSS and image files are available, so that PHP or database-based changes are only possible with paid packages such as Discord Community or Discord Team. This affects the documentation capability of dynamic project changes.

Requirements for Discord Bot Documentation

For documentation of changes such as file and configuration changes, PHP and databases (for paid packages) are required. Free packages only deliver static HTML, CSS and image files, not dynamic components for bot documentation. The change tracking takes place directly via the panel interface. You can find the appropriate entry under [Discord Bot Hosting].](/discord-bot-hosting/).

Paid packages for advanced changes

For extensive documentation of changes you need the paid package 'Discord Community' (2.49 EUR/mo) or 'Discord Team' (4.99 EUR/mo) both offer PHP and databases for structured project management tools. The free packages only deliver static HTML, CSS and image files without these functions.

The cost-paying packages allow the use of PHP and databases to systematically document changes to your Discord bot. This is required for complex configurations such as bot updates or database interactions that are not supported in free web hosting.

Documentation of configuration changes

With the /Discord-bot-hosting/-system you can understand all configuration changes for Discord bots via the Linux environment directly in the panel interface. The tools provided such as PHP and databases (for paid packages) allow structured documentation of the project files.

For detailed tracking of changes, use SFTP or SSH access to edit and document configuration files such as the bot file (e.g. bot.js) or database configurations. The isolated Linux environment ensures a clear separation of projects within the container.

Free packages do not provide database functions, so complex configuration changes are only possible with paid packages (e.g. Discord Community). This is crucial for the complete documentation of changes in the Discord bot project flow.

Restrictions on free packages

Free web hosting offers only 50 MB for static HTML, CSS and image files. PHP and databases are not included in the free package, which makes changes like bot configurations or dynamic file updates more difficult. Thus, documentation of changes is limited to the basic structure.

Without PHP or database access, you cannot make complete configuration changes for Discord bots. This limits the traceability of changes, as complex bot structures and server internal processes cannot be documented. The Linux environment remains available, but functionality is limited.

The free version does not allow automated change tracking tools such as versioning or logging. You need to manually modify and document files via SFTP/SSH, which is inefficient for large projects and may hide sources of errors. For professional documentation, paid packages are required. For more steps, see [Help Center].](/hilfe/).

Documenting changes with a comprehensible course

Run a short list of dates, changes, responsible person and test result per project. References to the affected instance or configuration file. For recurring tasks, a checklist that is known in the team is sufficient and updated after an actual test.

Also note where the last working backup is located and how a recovery is checked. Keys, tokens and passwords are documented separately in a protected memory. The operating documentation only mentions responsibilities and the intended access path. Thus, a new team member can understand the process without having confidential values in general notes.

Separate planned changes from already confirmed steps so that a later look into the course does not allow false conclusions.

Frequently asked questions

How do I document the accesses to my Discord bot in the /Discord-bot-hosting/system?

Plan the management of the bot as a team task: Who changes commands, who can stop the bot and who takes over a fault? Document these responsibilities separately from the secret access data. A technical deployment does not replace moderation rules for your community. First, test new answers and role actions specifically so that members can understand what a command does and what information becomes visible to the public.

What tools are needed to track changes to my Discord bot?

For file and configuration changes, you need SFTP or SSH. For paid packages, PHP and databases are available to keep the project structure transparent.

Are there any restrictions on free packages in the documentation of changes?

Free web hosting offers only 50 MB of static HTML, CSS and image files. PHP and databases are only available when paid packages are available, making documentation more complex.

How does the security of the isolated Linux environment work for my Discord Bot documentation?

The managed Discord Bot hosting is served in the customer panel. The options offered include start, stop and restart, configurable commands, and welcome and role functions in the respective scope of services. Do not confuse this area with a self-managed VPS. Root access and the administration of your own Linux system are your own requirements; they should not be derived solely from booking a bot package.

More hosting topics