Nassella has an unusual design constraint: no SSH, or server login of any kind. Nassella deploys immutable instances for self-hosting. If something goes wrong, you can't login to diagnose and fix it. The only option is to replace the instance with a new one. So how do
How much do you trust your backups? Yesterday, I put that to the test with Nassella: I deleted all of the data for the Nassella instance that hosts this blog and the Nassella Wordpress site. After confirming all of the sites were completely offline and not responding, I proceeded to
Mission: make self-hosting accessible to everyone! Problem Space: self-hosting is hard! It provides benefits like having control over data and software but deploying and maintaining a secure web server is difficult or impossible for most people. Nassella exists to automate the entire operational layer while still keeping users
The most recent major change to Nassella was to refactor (re-do) the way end-user apps (like NextCloud, or Ghost) are added to Nassella. The original way I created for adding apps worked but was very tedious and error prone. I always start out by just doing things the
Nassella is made up of three major components: a multi-tenant web app, control plane instances, and immutable instances that host the end-user applications. Applications that are deployed with Nassella live on an immutable instance. So if you deploy Nextcloud to cloud.example.org then users who visit cloud.
Nassella allows you to easily host web apps, but which web apps? The long-term goal is to allow running nearly any web app but, starting out, I have selected a small number to target. They are: NextCloud, wg-easy, and Ghost. (Dozzle, the log viewer web app is also