<deedoo>
does sandstorm use some sort of virtualisation?
<ocdtrekkie>
@deedoo, Sandstorm is more similar to container systems like Docker than virtualization systems.
<deedoo>
I don't really like docker
<deedoo>
especially to host some sites since many people do not recommend hosting in docker for a production server
<deedoo>
could a sandstorm deployed server scale?
<deedoo>
some people say that apps are not updated frequently
<deedoo>
is there something that prevents me from updating the apps manually?
<deedoo>
either over CLI or through the web-app itself if it has an update feature?
<mnutt>
Sandstorm uses some of the same linux system calls that docker does, but is _far_ more locked down than docker. Docker is fine for apps that you write or trust, but generally not meant for running apps you don't trust. Sandstorm is specifically designed such that you don't have to trust the apps you run on your server.
<mnutt>
I probably share some part of the blame for "apps not updated often" :-( as Davros wasn't updated for quite a while although I'm updating it now.
<deedoo>
eyy I can understand that it is an incredible amount of work maintaining apps and keeping them up to date
<mnutt>
I think whoever said that probably means "app authors don't update their apps often" which certainly be annoying for users, but Sandstorm's security models means that you are less likely to be at risk from running outdated apps than on other platforms.
<deedoo>
I was just wondering about the technical aspects of updating an app
<mnutt>
it's not possible for anybody but the author to publish an app to apps.sandstorm.io, but very possible for someone to download an app's source from github, make changes, and upload it to their own server.
<mnutt>
speaking of apps.sandstorm.io, is it possible to retract an experimental app version? or would pushing a new version automatically replace it?
<isd>
mnutt: I would advise bumping the appVersion field again. And maybe note to ocdtrekkie that he should not approve the bad release.
<mnutt>
cool, thanks
<ocdtrekkie>
Yeah, newer versions should replace it.
<ocdtrekkie>
We recommend always incrementing appVersion, otherwise the old version might get accidentally shown instead of the latest appVersion.
<isd>
deedoo: the reason so many aps are out of date is just that we as a community have a lot less manpower than we did when Sandstorm was maintained by a venture-backed startup. There used to be 3 full-time developers doing packaging, so a lot of the stuff they maintained is very out of date. We could definitely use extra hands.
<ocdtrekkie>
If there are multiple instances of the same app in the submission queue, I reject all but the latest.
deedoo has quit [Quit: Ping timeout (120 seconds)]
<ocdtrekkie>
Nobody has yet pitched a fit about us ever hosting open source apps without matching source, but I try to be ready for that day, lol.
<mnutt>
yeah that probably makes sense
<ocdtrekkie>
I'll put out a mailing list email asking for people to test 0.30.0. I probably don't have time to experiment with every conceivable edge case.
<mnutt>
I still wish for some sort of CI automation for building packages
<ocdtrekkie>
The guy who packaged Monica did some pretty fancy pipelining.
<mnutt>
so maybe we hold off on asking people to test? 0.30 solves a _lot_ of the outstanding issues, but 0.31 will solve what I consider the largest one, corrupted uplods
<ocdtrekkie>
We are statistically likely to be two weeks from that patch being released to Sandstorm.
<ocdtrekkie>
We can if you like. Though if people find new bugs in 0.30.0, you can fix them at the same time as 0.31.0. ;)
<mnutt>
fair enough. at least 0.31 will only change _one_ thing (chunked uploads)
<mnutt>
yep
<ocdtrekkie>
I haven't used an ownCloud client with Davros in years, but unreliable uploads was why I stopped.
<ocdtrekkie>
So I will probably try again once that version drops.
cwebber has quit [Remote host closed the connection]