I’m a big fan of Sandstorm. At the same time I understand that not every Wekan users want to use it, and prefer more traditional hosting and administrating using either Docker containers or vanilla NodeJS+MongoDB installation. I have also encouraged Wekan integration on various cloud platforms.
Sandstorm has improved significantly since my first Wekan package on it more than a year ago. It is the easiest platform for installing and updating Wekan. It’s way most secure than alternatives. And it’s about to get even better.
The Sandstorm shell will indeed soon receive its Powerbox UI that is really at the core of the platform design. In short, it will make an application like Wekan more powerful by being able to have some solid integrations with services provided by third-party applications.
I believe that using the full potential of the Sandstorm platform would benefit Wekan. However it will become difficult to maintain different feature implementations for different platforms. Things like sending an email, registering a user, uploading an attachment file, backing up the data, sending usage statistics to a third party application, and many other desirable features will have very diverging implementations on Sandstorm versus other platforms.
So as the Wekan lead developer, I wonder if we should focus Wekan development to support Sandstorm exclusively. I’d like to heard from users using Wekan on Docker or with vanilla-installation, what will need to be improved about Sandstorm before they consider a switch. To give an example I think that it is not easy to host a public board with a clean URL (http://myproject.io/roadmap) on Sandstorm. I’d like to learn more of these edge cases from Wekan users, I would also like to read what other teams like Rocket.Chat are thinking on the matter. And if there is any question arising about Sandstom capabilities, I’m confident that their core team will provide some valuable responses.
If you don’t know Sandstorm, I recommended reading the “How Sandstorm Works” article.