How to use the file manager on Schokr

The file manager lets you work with your server's files in your browser: upload files, edit configs, create folders, rename, move and delete. It is the main way to get your own files onto an Schokr server.

Opening the file manager

Sign in at console.schokr.gg.
Open your server.
Go to the Files section.

You start in your server's root folder, which is the folder your server runs from. Click a folder to open it and use the path at the top to go back up.

Uploading files

Open the folder where the files should go, for example plugins on a Paper server.
Use the upload option and pick files from your computer, or drag and drop them onto the page.
Wait for the upload to finish before leaving the page.

Uploading many files or folders? Zip them on your computer first, upload the single archive, then extract it on the server. It is much faster and keeps the folder structure intact. See archiving and unarchiving files.

Editing files

Click a text file, such as server.properties, config.yml, .env or package.json, to open it in the built-in editor. Make your changes and save.

motd=Welcome to our server
max-players=20

After saving, restart the server so it reads the new settings. Some software rewrites its config on shutdown, so for those it is safer to stop the server, edit, then start it again.

Creating, renaming, moving and deleting

New file or folder: create it from the file manager, for example a .env file for a bot.
Rename or move: rename a file, or change its path to move it into another folder.
Delete: select one or more files and delete them. There is no recycle bin, so take a snapshot first if you are unsure.

Downloading files

You can download individual files to your computer. To download a whole folder, such as a Minecraft world, archive it first and download the archive.

Good habits

Stop the server before replacing important files like world folders or databases. Changing them while the server is running can corrupt them.
Do not upload node_modules or virtual environments. Upload your code and let the server install dependencies. These folders are huge and are often built for a different operating system.
Watch your disk space. Everything you upload, plus archives you create, counts against your server's disk limit. See disk full errors.
Keep secrets out of shared files. Bot tokens and API keys belong in a .env file or Startup variables, and only trusted team members should have file access.

Prefer a desktop app? Use SFTP

For big uploads, lots of files or editing in your own editor, you can connect with an SFTP client like FileZilla, WinSCP or Cyberduck instead. See how to connect to your server with SFTP.

Permissions

File access is a team permission. You can give someone read access to files without letting them edit or delete. See team roles and permissions.