dboxedio

Run your cloud workloads on any server you like.

An Open Source cloud alternative that can be self-hosted or as a SaaS.

Built and bootstrapped by @codablock

[Alexander Block @codablock]

Just released v0.8.0 of Dboxed, allowing you to use Git as the source of box definitions. So you can now write down the box spec inside a file called "dboxed-specs.yaml" and Dboxed will create the actual boxes and volumes from them.

Proper docs will follow tomorrow.

I'm also at the point now where I should start thinking about development and release processes. For example, releases should now start having changelogs and migration infos/guides.

[Alexander Block @codablock]

This demo shows the latest features implemented into dboxed. You can now create Load Balancers and run them on ordinary machines. These LBs can then expose any box to the public internet, even if the box itself is behind a firewall or NAT. #buildinpublic

[Alexander Block @codablock]

Never been happier to see this page load successfully.

Not released yet, but it's basically done! Dboxed now has ingress support, allowing you to expose any box to the public internet.

#buildinpublic

[Alexander Block @codablock]

First time I created a demo recording for @dboxed_io.

It will walk you through some of the most important features of dboxed: creating and running boxes, with volumes being attached and then migrating a box from Hetzner to AWS without much effort. Using n8n for this demo.

[Alexander Block @codablock]

Dboxed blog is live, and first article available:
https://t.co/KyafAvESd8

I'm super nervous :D

[Alexander Block @codablock]

Just finished the first raw version of the self-hosting guide: https://t.co/dVkWp7rbCS
This guide is using @dexidp as the identity provider. I really like its simplicity, its the only one I know where you can define a list of static users without the need to have a complex setup.

[Alexander Block @codablock]

Docs for https://t.co/lPrS6tCdI1 are getting better and better.

Volumes are documented pretty good now, just check out https://t.co/VI4qIPadOy.

Docs for the Netbird integration is also done: https://t.co/FnTl9xrvN0.

Turned out that networks are so easy to use that the docs got quite short in that regard 😎

[Alexander Block @codablock]

And it's done. S3 buckets are now not part of volume providers. A volume provider now just refers a S3 bucket, allowing me to use S3 for future features as well.

I'll have docs and examples for dboxed volumes ready later today, stay tuned! :)