ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Most Discloud deploy failures trace back to a malformed discloud.config or a bad MAIN path. Here's the minimal working config, correct zip structure, upload options, and how to verify the app actually started.
A practical look at hosting a Discord bot on Discloud: how the discloud.config file drives deployment, what the CLI upload actually does, and where the resource limits bite.
Stop the cycle of random bot restarts. Learn how to properly configure discloud.config to align your RAM limits with your runtime and avoid OOM crashes.
Resource Management in discloud.config Discloud utilizes a discloud.config file to define application parameters, including the main entry point and versioning. While the platform manages resource limits based on the user's specific plan tier, the configuration file primarily focuses on application metadata rather than explicit resource requests. When transi
Managing application updates on Discloud involves modifying the discloud.config file and pushing new builds via the CLI. Because the platform utilizes an ephemeral file system for standard bot hosting, the current deployment process overwrites the existing runtime environment. When a new deployment introduces a breaking change or a configuration error that p
nodejs