Shlink is in; two other apps stayed out, on purpose

One app shipped, two were turned away, and the reasons say a lot about how PicoPaaS is built.

Share

We just ran another round of real-world apps through PicoPaaS. One went in, two stayed out, and we think the reasons are the interesting part.

Shlink is a self-hosted URL shortener, and it runs on PicoPaaS today. It's the public image with no custom build. It uses the platform's managed MySQL over TLS, it's configured entirely with env vars, and it runs as non-root. That's the whole model working as intended. The setup is written up as a recipe: platform.picopaas.xyz/guide/recipes.

A security note: pull first, restore on the fix

While Shlink was up, a vulnerability was disclosed in an underlying dependency, the PHP runtime. We took the app offline right away and brought it back only once the patched release was available. We run the patched version now. We'd rather pull something first and restore it on the fix than leave it exposed while we wait and see.

Evaluated, and turned away on purpose

We tried two others and declined both, because fitting them in would have meant relaxing the platform's safety rules.

  • FreshRSS (an RSS reader): the image we could use only runs as root. PicoPaaS requires non-root, so it didn't go in.
  • Wiki.js (a wiki): it ran cleanly, but its database migrations conflicted with a data-integrity default our managed database enforces. We weren't willing to loosen that guarantee for every tenant to suit one app, so we left it out.

The boundary is a feature

PicoPaaS hosts what fits its model: non-root, state kept outside the container, security first. We'd rather be upfront about what doesn't fit than quietly bend the rules. Every app we don't loosen the platform for is one more guarantee that holds for everyone running on it.