aligning expectations

It can be hard to explain what Solidbox is.

One way it can be hard is when the audience "kinda" get it, and then getting across the missing parts.

These are notes trying address that kind of mistaken expectations.


Someone already familiar with Solid might assume that it is Solid-in-a-box.

It is, but that's not really all, and arguably it is not the most exciting part:

Beyond being away to distribute and host Solid, Solidbox is also about wrapping conventional services to be data-driven, and data-driven system administration.


System administrators might assume it is a locally administrated box.

That's true but then again it isn't really:

It's a locally hosted system but without administration in the conventional sense. Instead the box rely on pre-packaged configuration adapting fully automatically by detecting usage patterns.


Those familiar with automated deployment of hosted services might recognize Solidbox as a system applying automation similar to CFEngine, Puppet, and Chef.

While it is true that custom scripting is developed specifically for the system, that is only intended as a temporary workaround. A Solidbox system never fetches code directly from upstream but installs only curated pre-build and pre-packaged code from Debian. Goal is to replace all custom scripting with debconf enhancements of distributed software packages.