How to Extend, Back Up, and Support Atheos Cloud IDE

Updated

Atheos Cloud IDE is an open-source, web-based IDE with a plugin library and marketplace, quick-download backups, and a fully customizable source base. You can extend it through plugins, back up your code with a quick download, and support the project through GitHub Sponsors or BuyMeACoffee. These options are documented on the official Atheos site; specific plugin availability and backup behavior depend on your installation.

Extending Atheos with Plugins

Atheos ships with a Plugin Library & Marketplace, which is the primary way to add functionality without modifying core files. The site lists this as a built-in feature alongside error checking, multiple user support, and real-time collaborative editing.

To use it:

  1. Open Atheos in your browser and log in.
  2. Access the hidden right panel, which contains system, plugin, and other controls.
  3. Browse the plugin library or marketplace from there.
  4. Install the plugin you need.

The expected result is that the plugin's features become available in your editor or workspace without a manual code change. A common snag: because Atheos runs on your own server with basic read/write access, plugin installation depends on those directories being writable. If a plugin fails to install, check file permissions first.

Customizing the Source Directly

Because Atheos is completely open-source and its source is easily customized, you can also extend it by editing the code itself. This suits teams that need behavior the plugin library doesn't cover. The trade-off is maintenance: direct edits can complicate upgrades, so keep a record of your changes.

Backing Up Your Code

Atheos offers Quick-Download backups. This lets you pull your work down rather than relying solely on the server. The site also mentions LocalStorage redundancy, which provides an additional layer of protection for editor content in the browser.

A practical routine:

  • Use quick-download backups at meaningful checkpoints (before major refactors, before plugin changes).
  • Treat LocalStorage redundancy as a safety net, not a replacement for downloading your code.
  • Since Atheos has no database requirement, your files live in the server's file system — so server-level backups of that directory are also worth having.

Supporting the Project

Atheos is maintained by Liam Siira, who states it is his main coding environment and that he has no plans to switch. He fixes bugs and adds features as fast as he can.

Ways to support it, per the site:

Method What it is
GitHub Sponsors Recurring or one-time sponsorship via GitHub
BuyMeACoffee One-time support page
Email Sharing use cases and real-world usage, which the maintainer says he appreciates
GitHub Following the repository for the latest changes and news

If you want to track development or contribute, the GitHub repository is the place for updates. The site explicitly points there for "the latest changes and news."

What This Means for Your Decision

  • If you need extra features: start with the plugin library and marketplace; fall back to source customization only if needed.
  • If you care about data safety: combine quick-download backups with server-side backups of the install directory.
  • If you want the project to continue: GitHub Sponsors and BuyMeACoffee are the stated support channels, and GitHub is where updates are announced.

Atheos requires only Apache2, PHP 7+ (tested on PHP 5.4, with active development on PHP 7), and basic read/write access — no database. That minimal footprint is what makes both self-hosting and customization straightforward.