1. 15

  2. 28

    The title of this submission is incorrect. We are not “leaving Sandstorm to OSS contributors”. I, the founder of Sandstorm, am fully committed to continue leading the project. This project is “my baby” and I’m not going to give it up just because it isn’t paying me a salary. Many successful open source projects are built by people who have unrelated day jobs.

    1. 2

      Just wanted to stop by and say thanks!

      I love how slick the setup for supported apps is.

    2. 3

      I looked at Sandstorm early on, and one of the reasons that I didn’t jump into it then (and haven’t since then either), is that it’s all built on MongoDB. I’m not trusting my personal data to MongoDB under any circumstances. I can appreciate the goal, but it needs to be built on more robust foundations.

      1. 6

        Mongo is used to store metadata, but apps store their own content in whatever format they prefer. We used Mongo for metadata primarily because we wanted to use Meteor as our reactive web framework, and at the time it only integrated well with Mongo. I’d like to move away from it in the future, but this is really an implementation detail…

        1. 4

          Apologies, but implementation details matter.

          If the underlying data storage for Sandstorm is trivial, then what exactly does using Sandstorm vs using the apps that sit on top of it buy me? Half of the apps in the Sandstorm “app store” are things that are also usable outside of the Sandstorm ecosystem.

          1. 7

            Sandstorm automates the process of installing, updating, and securing apps, to the point that a non-technical user can do it, whereas if you deploy them all separately you’ll need to spend a lot of time on each of those things for each app and you’ll need technical skills.