BigShip has quit [Remote host closed the connection]
msoucy| has joined #sandstorm
citruspi has joined #sandstorm
sugarpuff_ has joined #sandstorm
msoucy has quit [Ping timeout: 246 seconds]
msoucy| is now known as msoucy
fkautz has quit [Ping timeout: 246 seconds]
XgF has quit [Ping timeout: 246 seconds]
_citruspi has quit [Ping timeout: 246 seconds]
sugarpuff has quit [Ping timeout: 246 seconds]
XgF has joined #sandstorm
sugarpuff_ is now known as sugarpuff
mnutt_ has joined #sandstorm
fkautz has joined #sandstorm
jemc has joined #sandstorm
xet7b has joined #sandstorm
xet7_ has quit [Ping timeout: 276 seconds]
<azirbel>
got a couple questions about app packaging. I've been making some decent progress, leaning pretty heavily on davros, paperwork, and loomio configs (thanks so much, packagers!)
<azirbel>
question 1: I see a lot of `apt-get install X` in setup.sh files. What happens if a new version of some package is released? Won't this suddenly break the app? A lot of times, configurations/paths seem to depend on very specific versions. For example, https://github.com/ndarilek/loomio-sandstorm/blob/master/.sandstorm/build.sh#L28
<azirbel>
I'm a little confused whether `setup.sh` is only being run on my dev machine, or if those `apt-get install` commands will be running on everyone's server. It sounds to me like the script will be running on other people's servers and pulling down the latest version of all those apt-get dependencies, which feels pretty weird
<azirbel>
question 2: is there much difference between, say, `npm install -g bower && bower ...` and `npm install --save bower && ./node_modules/bower/bin/bower ...`?
<azirbel>
I don't really _need_ answers to either of these things, but just curious.
<zarvox>
azirbel: the VM images these are based on is built atop Debian stable, which generally does not ship breaking changes within a release.
<zarvox>
setup.sh is only ever run by your dev machine, to prepare the VM.
<azirbel>
ohhh ok! thanks zarvox!
<zarvox>
as for the npm question: I tend to prefer the second form, which lets you keep project dependencies isolated
<azirbel>
what do you mean by isolated? I can see how it's nice to have a description of the dependencies in package.json
<zarvox>
Basically, the package-building process needs to collect *all* the files that will be a part of the .spk package, which is a hermetic bundle of all the code that your package needs to run
<zarvox>
If I have two node projects, and one requires bower at v1 and another requires bower at v2, that's possible in the latter setup
<zarvox>
there can be only one globally-installed version
<azirbel>
gotcha
<zarvox>
Granted, this is fairly rare for the sort of things that you install with npm globally
<zarvox>
Sandstorm takes a very app-centric view of the world. In a sense, the VM and everything you install with apt are just libraries that you're pulling in as app dependencies, and this is perhaps the most convenient way to fetch/configure/run them all
<zarvox>
Any other questions I can answer for you? :D
<azirbel>
so if I npm install something, but then never use it, will it be effectively discarded from my app package?
<azirbel>
(npm install in setup.sh)
<zarvox>
"probably" unless you specify a containing folder to be alwaysInclude'd in your sandstorm-pkgdef.capnp
<azirbel>
cool! that's all the questions I've got, thanks again!
<zarvox>
The files that get included in your app package are precisely: 1) the files in sandstorm-files.list, a list built by tracing the files accessed by launcher.sh (and its children) plus 2) things specified in alwaysInclude
<azirbel>
I've clearly gotten too used to the "...person is typing" messages in slack and have forgotten to give enough time for responses...
<azirbel>
ah ok. I haven't learned about alwaysInclude yet
<zarvox>
Heh. Perhaps some day we will provide a public-facing Rocket.Chat on Sandstorm :)
<zarvox>
azirbel: Also, another big thanks for the rad mockups you posted! Thanks for starting a lively and productive discussion!
<azirbel>
:D thanks for the reply! everyone's brought up a lot of great points. I'm really amazed by the discussion
<zarvox>
Me too! It's super heartwarming :)
jemc has quit [Ping timeout: 248 seconds]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<zarvox>
looks like it can't mix user namespaces and mount-y things as root; otherwise, it looks like it can do basically all the things the Sandstorm sandbox does
phildini has left #sandstorm [#sandstorm]
raoulzecat has quit [Ping timeout: 260 seconds]
Battleking has joined #sandstorm
Battleking has quit [Client Quit]
decipherstatic has quit [Ping timeout: 260 seconds]
decipherstatic has joined #sandstorm
asmyers has joined #sandstorm
pdsn has joined #sandstorm
<pdsn>
hi!
<pdsn>
I noticed a issue when using email to sign in to sandstorm - it appears to be case sensitive. I thought I'd lost my initial account, but actually I now have two accounts. Anyone else seen this behavior?
<kentonv>
pdurbin: Thanks! Looks like they start talking about it shortly after 38:50.
jemc has left #sandstorm ["WeeChat 1.4"]
<zarvox>
frigginglorious: when I'm testing locally, I usually just apt-get install postfix and then point Sandstorm at localhost:25, and then send mail to an account that doesn't bother with spam-filtering
<zarvox>
halindrome: mnutt_ is the author of Davros, and he idles here. Probably as good a place as any :)
<frigginglorious>
zarvox: thanks. I was looking at it, but I had been meaning to test SendGrid anyway, so i hooked that up :P
<halindrome>
mnutt_: the question was pretty simple: If I have created a sharing link (as opposed to an invite) how can I view it / send it out to others?
<halindrome>
right now the list of sharing links let's me change the name, but I don't see how to view the link token
<mnutt_>
I believe that when you create the sharing link, it is only shown on creation. it's a security feature of sandstorm that sandstorm itself does not record the link
<mnutt_>
so I would probably just generate a second link
<simonv3>
^ I have never experienced the issue described above, but the user says that everyone was seen as an “owner” of the survey, and that they were experiencing this on 153, but now it’s not an issue anymore, and they checked the version of Sandstorm they were using and it was now 155.
<simonv3>
So I decided to ask here if anyone thought of something, do I suspect a Meteor hiccup before that
<simonv3>
though* I suspect a Meteor hiccup, rather