Set Up a Server

Upload your files, review startup settings, and prepare your deployment to run.

Updated Jul 7, 2026

Before you start

Set up your deployment

The new panel does not include shell access.

The console also does not support install commands.

Do not run npm install discord.js or pip install discord.py there.

After you create the deployment, open its panel.

Use the tabs at the top to manage files, startup settings, and access details.

If you created the deployment from GitHub, a ZIP file, a backup, or a template, some files may already be there.


Upload your files

You only need one upload method.

If you already uploaded a ZIP archive, selected a backup, or cloned a GitHub repository, and you already have all required files, you can skip this section.

Choose one method:

  • Files — Upload files directly in the Files tab.
  • SFTP — Manage files from your computer with an SFTP client. Use the credentials in the SFTP tab. You can also follow Connect to your server's files with SFTP.

Always keep a copy of the original files on your device, in cloud storage, or in a Git repository.

If your account or deployment is deleted, those files are lost too.

If you upload from Files, follow these steps:

  1. Open Files.
  2. Upload your archive or project files.
  3. Extract the archive if you uploaded one.
  • If you use Node.js, do not upload node_modules.

    Upload package.json instead.

  • If you use Python, do not upload .cache or .local.

    Upload requirements.txt instead.

  • Compressed files such as .zip or .gz are usually the easiest option.

Archives often extract into a new folder.

Move the project files out of that folder so the main files stay in the root directory.

You can drag files out one by one.

You can also select multiple files and move them together.

Delete the archive and extra folder after the move to free up space.


Review startup settings

Open Startup before you start the deployment.

Check Entry File (STARTUP_FILE).

It must point to the main file that starts your app.

If the startup file is inside a folder, enter its full relative path.


Install dependencies

For Node.js and Python, the deployment reads dependency files during startup.

Node.js

Use package.json or the Packages tab.

Using package.json:

The deployment installs packages from the names and versions listed there.

You can upload the file from your local project, or create one with the npm package.json guide.

- npm install package (not supported here)
+ package

Using the Packages tab:

Enter the package name in the field, select it from the list, then click Add.

Repeat until you add every package you need.

Common Node.js errors

  • Error: Cannot find module 'package'

    The package is missing from package.json, or installation failed earlier.

  • npm error 404 Not Found - GET https://registry.npmjs.org/

    The package name is invalid, misspelled, or unavailable.

Python

Use requirements.txt.

The deployment installs packages from that file when it starts.

Format the file with the requirements.txt reference.

- pip install package (not supported here)
+ package

Common Python errors

  • ModuleNotFoundError: No module named 'discord'

    The package is missing from requirements.txt, or installation failed earlier.

  • ERROR: Could not find a version that satisfies the requirement package (from versions: none)

    The package name is invalid, misspelled, or unavailable.

Start the deployment

Once your files and startup settings are ready, start the deployment and check the console output.

If startup fails, check the file path, dependency files, and package names first.