Skip to documentation
Interneting.orgDocs

Documentation

Managed applications

Install and manage supported applications and Custom Image workloads.

Use Applications to install, adopt and manage supported software on a Control Site.

Choose an application

The catalogue includes Micro CMS, WordPress, MediaWiki, Ghost, n8n, PocketBase, Nextcloud, Immich, Joomla, Drupal, PrestaShop, Shopware, Directus, Strapi, Craft CMS and other supported applications. Choose Custom Image when you have a compatible container image that is not in the catalogue.

Application cards describe the actual runtime, database needs, setup inputs, source and update responsibility. Some applications need additional setup in their own interface after Control finishes provisioning them.

Install

  1. Select the application.
  2. Choose a new Site or an eligible existing Site and application path, where offered.
  3. Provide the required setup details. Keep any generated administrator credentials secure.
  4. Review the plan and start the installation.
  5. Wait for Control to report the result, then finish the application's own first-run setup when needed.

Control prepares the supported runtime and data connections for the selected application. The application remains responsible for its own content, users and settings.

WordPress and Micro CMS

These can run on supported PHP Sites. Choose Adopt Existing where Control offers it if you already have a working installation you want to bring under management; adoption is not a reinstall. Multiple applications can share a Site at separate paths when the selected application supports that layout.

MediaWiki

MediaWiki installs on a PHP Site with a managed MariaDB database. Provide the wiki name and first administrator details during installation, then manage pages, users and extensions from MediaWiki.

My Recipes

My Recipes stores reusable private deployment definitions for workloads you manage yourself. Saved recipes can cover Custom Image, Compose and supported native PHP/Node definitions. Editing a recipe creates a new revision and does not rewrite Sites that were already deployed from an older revision.

Container applications

Applications such as Ghost and n8n may have private database or storage services. Control manages their Site, HTTPS and persistent data connections; use the application's own setup or export tools when needed.

Updates and reinstalls

Use an application's supported update or reinstall action when available. Check its release notes and have a suitable backup before upgrading stateful applications. Applications marked operator-managed are not silently replaced by Control.

Remove or delete

Delete Application is destructive and removes its application-owned private data by default. Choose Remove Application, Keep Data only when you deliberately need its retained data for a future reinstall or recovery. Deleting the whole Site also removes resources owned by that Site.

Deploy Archive

Eligible Sites can deploy an application ZIP to a selected path. Matching files may be replaced; review the destination and take a backup before overwriting a working application.

For more help, see Micro CMS, MediaWiki, My Recipes and Application private data.