Skip to content

Index

Starting and Stopping Apps

Rationale

Running Apps on Portal is realized through docker-compose. When you install an app, the docker-compose.yml that contains all apps is rerendered and the process restarted. This causes docker-compose to pick up the new app and to pull it and start it.

However, until recently that meant that every app you have installed is running all the time. This limited the number of installed apps severely as the bottleneck was the Portal's RAM - 1GB with the current setup.

New features for the Portal App store

⚠️ If you own a Portal, restart it now, and it will upgrade itself. (Use the settings menu on the top-right.)

When we first designed the app store, we focused on building something that works quickly. It was always meant to be a first shot that would be extended or replaced at some time. We now felt compelled to address this task.

Getting rid of Registration and Login Views

We are continuously working on bringing more apps into our app store. But since we are using apps that were originally made for self-hosting, we often need to make some tweaks. In particular, we want the user to be able to open an app after installation without the need to go through a registration or login form. Each Portal is mainly a single-user platform so that would be quite confusing.