271–280 of 342 posts
The cloud space is absurd, we've sat by for 2 decades while the likes of AWS define every aspect of deployment, auth, even containerisation. Containerisation was supposed to mean host anywhere, literally redeploy a complex set of services and their connections on any cloud provider at the drop of a hat. That is what a f**ing shipping container is, you rock up to any port in the world and the same container is lifted…
Earlier quoted context omitted.
You are also characterizing another project that was open-sourced (sandstorm) and is under active development as "long abandoned". Open source is difficult and requires a fair amount of cheerleading to engage users and make them part of the community. As a result it's hard to see your project in a positive light.
I mean, to be honest it does look like sandstorm development has almost stopped for the past couple of years...or am I missing something? https://github.com/sandstorm-io/sandstorm/graphs/code-freque...
These guys have been spamming issues in repos trying to promote this project and no disclosure whatsoever that they are associated with the project. https://github.com/search?q=%22cloudinabottle.toml%22&type=i...
Running the authoritative dns for the zone seems elegant, although wouldn’t that imply you absolutely can’t use cloudflare or similar services to avoid ddos/bots?
The cloud space is absurd, we've sat by for 2 decades while the likes of AWS define every aspect of deployment, auth, even containerisation. Containerisation was supposed to mean host anywhere, literally redeploy a complex set of services and their connections on any cloud provider at the drop of a hat. That is what a f**ing shipping container is, you rock up to any port in the world and the same container is lifted…
This isn't the hard part of self-hosting, at least not anymore. In the comments here there are lots of examples of similar projects that solve basically the same problem (app selection and deployment). To make self-hosting "easy" we need to solve domain registration, DNS management, and port-forwarding configuration. This probably requires a project more like OpenWRT that includes an API-driven relationship with a re…
This isn't the hard part of self-hosting, at least not anymore. In the comments here there are lots of examples of similar projects that solve basically the same problem (app selection and deployment). To make self-hosting "easy" we need to solve domain registration, DNS management, and port-forwarding configuration. This probably requires a project more like OpenWRT that includes an API-driven relationship with a re…
These guys have been spamming issues in repos trying to promote this project and no disclosure whatsoever that they are associated with the project. https://github.com/search?q=%22cloudinabottle.toml%22&type=i...
The cloud space is absurd, we've sat by for 2 decades while the likes of AWS define every aspect of deployment, auth, even containerisation. Containerisation was supposed to mean host anywhere, literally redeploy a complex set of services and their connections on any cloud provider at the drop of a hat. That is what a f**ing shipping container is, you rock up to any port in the world and the same container is lifted…
I have coworkers who host personal projects for their own use and put them in docker, set up CI pipelines, host them on a cloud service, use an enterprise level database on the backend. One of my coworkers made a completely static portfolio website with a single page and used react.
I don't mean this in a judgemental way, people are free to use whatever they like. But it does sadden me that instead of seeing tools and processes as having certain benefits and certain overheads it's now just "this is the tool we use for everything", and therefore "everything now has this overhead". Where the overhead is performance, time, complexity.