Skip to content
Coritan Docs

November 2026

Update a Node.js or Python server from its git repository and roll back, and change, add and remove a server's startup variables.

View as Markdown

The changes to Coritan in November 2026 that you can use, newest first. Each one links to the guide that describes it.

Update a server from its git repository, and roll back

Section titled Update a server from its git repository, and roll back

A Node.js or Python server with a Git address on GitHub or GitLab now has a Releases tab. Deploy… puts a new commit on the server and keeps the files that are not in the repository, such as a .env file and installed dependencies. We fetch and check the commit before the server is touched, and if the new version does not stay up after it starts, the previous one is put back and started again. Rebuild… fetches the branch again and clears the dependency folder, Redeploy… puts the live release's files back, and Roll back to this… returns to an earlier release (Update a server from its git repository).

You can now set the token for a private repository yourself, on the Repository card of the same tab. It is stored sealed and never shown again.

Reinstall server… on such a server now fetches the repository before it deletes anything. Until now a reinstall deleted the files first, so a repository that could not be fetched, for example after its token expired, left the server with an empty directory. A reinstall that cannot fetch the repository does not start, and an install whose repository cannot be fetched no longer reads as finished.

In the API, the routes are under /api/v1/client/servers/{uuid}: GET and POST /releases, POST /redeploy, POST /releases/{release_uuid}/rollback and /cancel, and GET and PUT /git-token. The server's own read has a new git field.

Change, add and remove your server's startup variables

Section titled Change, add and remove your server's startup variables

The Startup variables card on a server's Settings tab now lets you change every variable, add your own with Add a variable, and Reset or Remove one you changed or added. Until now only a server's passwords and a few game settings could change, so an app server could not keep its own settings and keys there. A few variables stay with the platform (its memory, address and port), with the Java settings or with safe mode, and the card says so beside each. A free server keeps the program it runs as the panel installed it, and its values hold plain text only.

In the API, PATCH /api/v1/client/servers/{uuid}/startup-variables takes remove_variables beside variables, and GET says for each variable whether you can change or remove it, and why not (Server settings). A storefront's portal API has the same two routes (Let customers run their servers).