NewSchokr 13 is here. A whole new UI, seven locations, snapshots and more. Read more →

How to upload your app's code with the file manager

Upload your app or bot code to Schokr with the web file manager, use zip archives for speed, and know which files and folders to leave out.

Updated · 2 min read

You upload app code to Schokr through your server's web file manager in the console. For anything more than a handful of files, zip the project on your computer, upload the zip, and extract it on the server.

What to upload

UploadLeave out
Source files (src/, index.js, app.py)node_modules/
package.json and lock file, or requirements.txtvenv/, .venv/, __pycache__/
.env (your secrets, created or uploaded separately).git/
Build output, if you build locally (dist/, .next/standalone).next/cache, .turbo, coverage/
Static assets (public/, static/, templates/)OS files like .DS_Store, Thumbs.db

Dependencies are installed on the server, not uploaded. See installing dependencies.

Upload with a zip

  1. On your computer, create a zip of your project without the excluded folders.

On macOS or Linux:

zip -r app.zip . -x "node_modules/*" ".git/*" "venv/*" ".venv/*" "*.DS_Store"

On Windows, select the files and folders you need (not the whole project folder if it contains node_modules), then choose "Compress to ZIP file".

  1. Open your server in the console and go to the file manager.
  2. Upload app.zip.
  3. Extract it in the file manager.
  4. Check the files ended up where you expect. If everything is inside an extra folder (for example my-app/index.js), either move the files up or point your Startup settings at that folder's entry file.
  5. Delete the zip to save disk space.

Hidden files

Files that start with a dot, like .env, are hidden by default on macOS and Linux and are easy to miss when zipping or uploading. After uploading, confirm .env exists in the file manager. You can also create it directly in the file manager and paste in the contents.

Editing files on the server

The file manager lets you open and edit text files in the browser. That is handy for quick fixes to config or .env, but keep your real source of truth on your computer or in Git, or the next upload will overwrite your server-side edits.

Disk space

Your team's free pool includes 10 GB of disk shared across servers. Installed node_modules folders can be large, so delete old builds, logs and zips you no longer need.

After uploading

  1. Set the main file or startup command in your server's Startup settings.
  2. Start or restart the server.
  3. Watch the console for install output and errors.

For later releases, see updating your app.

Tip: for large uploads, you can also use an SFTP client like FileZilla. See how to connect with SFTP.