3 ms·
I'm not recommending any of these; I think it's best to just run services manually - with one VPS, Docker and something like Caddy the pain isn't that large. I
by akvadrako 6y ago
I'm not recommending any of these; I think it's best to just run services manually - with one VPS, Docker and something like Caddy the pain isn't that large.
It would be great if Sandstorm could get enough attention to thrive because it looked promising, but the activity of the blog¹ doesn't give me much hope. Since 2019 when it announced the hosting was shutting down there have been just 4 posts and apparently no major releases.
[1] https://sandstorm.io/news/ https://sandstorm.io/news/
- kentonv 6y ago> apparently no major releases I push at least one release each month. The change log is here: https://github.com/sandstorm-io/sandstorm/blob/master/CHANGELOG.md https://github.com/sandstorm-io/sandstorm/blob/master/CHANGE... But it's certainly true that development is much slower today than it was in 2016 when there were seven people working full-time on it.
- ocdtrekkie 6y agoWe probably should write another blog post or two. We generally try to only post substantial content to the blog, our mailing list tends to have a bit more of the mundane, and of course, our GitHub issues/PRs. Many projects make blog posts for releases, but we generally do not. For what it's worth, the "just four posts" constitute some major things: 1. Continuing Sandstorm as a community project 2. The 1.0 release of the main app packaging tool 3. Let's Encrypt support built-in 4. A major security improvement in disabling apps from making outgoing HTTP requests without permission