<wolcen>
puck2: apparently the defaults are TCP port 6080 and TCP port 30025
<wolcen>
puck2: 443/80 are listed as optional.
<puck2>
thanks, wolcen
<wolcen>
puck2: but you can see quickly which port it is on checking the sandstorm.conf
<puck2>
that is not accurate for sandcats.io
<puck2>
443/80 are the defaults
<puck2>
maybe doc is outdated?
<wolcen>
puck2: I'm not sure....I may not so helpful since I quit setting up locally and moved to a hosted solution for my own :P
puck2 has quit [Ping timeout: 240 seconds]
dwrensha has quit [Ping timeout: 248 seconds]
puck2 has joined #sandstorm
bb010g has quit [Quit: Connection closed for inactivity]
notevil has joined #sandstorm
jon1012__ has quit [Ping timeout: 240 seconds]
decipherstatic has quit [Remote host closed the connection]
|jemc| has joined #sandstorm
AsheeshRoam has joined #sandstorm
AsheeshRoam has quit [Client Quit]
xet7_ has joined #sandstorm
xet7_ has quit [Client Quit]
xet7_ has joined #sandstorm
xet7 has quit [Ping timeout: 240 seconds]
xet7_ is now known as xet7
joshbuddy has joined #sandstorm
rustyrazorblade has joined #sandstorm
xet7_ has joined #sandstorm
xet7 has quit [Ping timeout: 240 seconds]
puck2 has quit [Ping timeout: 240 seconds]
tdc has joined #sandstorm
tdc has quit [Client Quit]
puck2 has joined #sandstorm
canucky has joined #sandstorm
funwhilelost has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 255 seconds]
<asheesh>
Howdy puck2 btw
<asheesh>
& howdy canucky
<asheesh>
canucky: I see your email; will take a look
<canucky>
right on asheesh - thnx
TC01 has quit [*.net *.split]
asheesh has quit [*.net *.split]
niekie has quit [*.net *.split]
au has quit [*.net *.split]
dograt has quit [*.net *.split]
xobs has quit [*.net *.split]
jsilence has quit [*.net *.split]
sandah has quit [*.net *.split]
au has joined #sandstorm
asheesh has joined #sandstorm
jsilence has joined #sandstorm
sandah has joined #sandstorm
xobs has joined #sandstorm
niekie has joined #sandstorm
dograt has joined #sandstorm
elimisteve has quit [*.net *.split]
ripdog has quit [*.net *.split]
warren has quit [*.net *.split]
warren has joined #sandstorm
elimisteve has joined #sandstorm
ripdog has joined #sandstorm
TC01 has joined #sandstorm
<asheesh>
Hey canucky, if you're here, then maybe IRC is easier for latency reasons.
<asheesh>
1. You need to
<asheesh>
cd .sandstorm ; vagrant provision ; cd ..
<asheesh>
to re-execute setup.sh
<asheesh>
2. I'm going to adjust the docs to make that clearer.
<canucky>
still here ... great, thanks will do that
<asheesh>
3. If you update vagrant-spk, optionally, you'll find there are some improvements that make some of the configuration files easier to edit; for that reasons, I suggest doing 'vagrant-spk halt' then 'cd ~/projects/vagrant-spk ; git pull' then 'cd ~/projects/grav-spk ; then 'vagrant-spk setupvm lemp' to get a fresh set of .sandstorm/* files, then 'vagrant-spk up' again.
<asheesh>
You don't have to; it'll improve your life about 20%, which is a far cry from like 200%.
<canucky>
fantastic - thnx asheesh - will give it a shot later and let you know how it works out
<asheesh>
Great.
<asheesh>
Keep me posted; IRC is good if I'm here, else email is good too.
<asheesh>
Getting your issues is really important to me.
<asheesh>
I know like every customer service person says that; I do mean it, fwiw!
<TheHobbyist>
I am interested in setting up a sandstorm server, but I have questions
<TheHobbyist>
Primarily, I am interested in using sandstorm alongside zfs
<asheesh>
Awesome, TheHobbyist
<asheesh>
ZFS + Sandstorm should work great.
<asheesh>
Here's how I'd do it:
<asheesh>
- Create a ZFS "volume" for /opt/sandstorm
<asheesh>
- Do an install via install.sh
<asheesh>
- Live a happy life where zfs snapshots & 'zfs send' works for backups/etc.
rustyrazorblade has quit [Quit: rustyrazorblade]
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Client Quit]
jadewang has joined #sandstorm
rustyrazorblade has joined #sandstorm
puck2 has quit [Ping timeout: 255 seconds]
<asheesh>
TheHobbyist: What do you think of the above?
<maurer>
asheesh: I'll note that while that would likely work, there's room for deeper fun if you wanted to - ZFS snapshots would provide a way to do ultra-fast grain creation
<maurer>
asheesh: And also allow for migration of grains via ZFS send/recv
<asheesh>
How would ZFS snapshots help with grain creation, fwiw?
<asheesh>
I think Sandstorm's use of mount namespaces obviates much of the benefit of snapshots.
<maurer>
asheesh: If you snapshot the app, any "template" resources can be created in COW form
<maurer>
asheesh: Basically, any resource which needs to be rw for correct operation, but will not necessarily be overwritten
<asheesh>
Right, like initial MySQL database or something like that.
<maurer>
Sure
<asheesh>
That makes sense, yeah.
<maurer>
This would get the app up and running a bit quicker, at the cost of the initial writes being slightly slower
<maurer>
which I _think_ might be a worthwhile tradeoff
<maurer>
Actually, I don't even know if the initial writes would be slower
<maurer>
it depends on things I don't know about how ZFS works
<maurer>
In any case, just using ZFS seems fine, but I could see some fun things to do with migration and fast grain creation
dwrensha has joined #sandstorm
<maurer>
ZFS would also be a strong candidate for a long term object store in the future, the only issue there being I'd assume you wouldn't want to pin your object store to requiring that
<dwrensha>
can someone remind me how to run the latest node-capnp outside of sandstorm/ekam land?
<maurer>
asheesh: In any case, I'm going to stop ranting, but if you're interested in doing something with ZFS integration, I can put you in touch with an OpenZFS dev
<dwrensha>
like, I can build it from source by doing `npm install` in the node-capnp directory, but then how do I use it from another project?
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
funwhilelost has joined #sandstorm
dwrensha has quit [Ping timeout: 252 seconds]
rustyrazorblade has quit [Quit: rustyrazorblade]
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Client Quit]
<ocdtrekkie>
dwrensha : Somehow, I missed your response this long. Self-driving cars aren't 'fast becoming a reality'. If you ignore Chris Urmson's marketing speak, they seem a decade away or more.
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<ocdtrekkie>
As Tesla put it: Making a car drive itself correctly 99% of the time is easy. One that works 99.999% of the time, however, is incredibly hard.
<ocdtrekkie>
Google's marketing on the Self-Driving Car programs is misleading at best, possibly outright deceptive.
<ocdtrekkie>
In twelve months the cars would've caused ten accidents if not for their human drivers, and in the same period the software failed out entirely and handed control back to drivers 272 times.
<ocdtrekkie>
They're far less safe than human drivers by the numbers Google reported to the DMV. A number they fail to highlight when they brag about how many miles their cars have driven.
dwrensha has joined #sandstorm
<ocdtrekkie>
I would go so far as to say it might be this generation's flying car. Something we keep getting told is just around the corner and never seeing.
<ocdtrekkie>
Oh. Lol. dwrensha, check the log. :/
<dwrensha>
ocdtrekkie: I think that I drive correctly way less than 99.999% of the time
<dwrensha>
the problem with flying cars is that flight costs a lot of energy
mnutt_ has joined #sandstorm
neynah has joined #sandstorm
funwhilelost has joined #sandstorm
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has joined #sandstorm
<ocdtrekkie>
dwrensha : But you're two or three times safer still than a self-driving car. And self-driving cars in the hands of consumers would be much more risky than the current tests, because consumers would trust them, and not be prepared to handle system failures like the trained test drivers are.
jadewang has quit [Remote host closed the connection]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has joined #sandstorm
puck2 has joined #sandstorm
<puck2>
when installing sandstorm on a fresh ubuntu server, what ubuntu components are needed beyond the core?
<ocdtrekkie>
Nothing, AFAIK, puck2
<ocdtrekkie>
Sandstorm is very self-contained. I think it pretty much bundles everything it needs besides the kernel. But I am not a Linux person, so my thoughts are not authoritative by any means.
wolcen has quit [Remote host closed the connection]
wolcen has joined #sandstorm
<puck2>
thanks for responding, ocdtrekkie
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
wolcen has quit [Ping timeout: 250 seconds]
nicolagreco has quit [Ping timeout: 240 seconds]
mnutt_ has joined #sandstorm
|jemc| has joined #sandstorm
notevil has quit [Quit: start weekend]
jadewang has joined #sandstorm
neynah has joined #sandstorm
jadewang has quit [Remote host closed the connection]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
* asheesh
waves
<asheesh>
puck2: Yeah, ocdtrekkie is correct; the install.sh script will detect any missing dependencies; as I recall, they are: openssl, curl, xz
<asheesh>
But it's very close to nothing at all. No nginx is required; no apache; no php, python, perl, etc.
donught has joined #sandstorm
<puck2>
i did not install any optional packages and install.sh did not flag anything
<puck2>
asheesh ^^
<asheesh>
Yeah, perfect.
<puck2>
except that i cannot make an ssl handshake with the server
<asheesh>
BTW, glad you're here and asking questions! I'm curious what you plan to use Sandstorm for!
<asheesh>
Oh
<asheesh>
Firefox, or Chrome?
<puck2>
ff
<asheesh>
If Firefox, and you're using sandcats, note that you have to wait ~10 minutes for GlobalSign to set up OCSP. Basically, it works in Chrome immediately, and then after 10 minutes, works A-OK in Firefox too.
<puck2>
i've waited 10 minutes and then tried before another 5 minutes elapsed
<puck2>
because admin-token says it expires in 15 minutes
<asheesh>
Oh yuck, yeah, we should make it last longer probably to avoid this problem/
<puck2>
repeated that process several times without luck
<asheesh>
Did you try in non-firefox, i.e. Chrome?
<puck2>
tried in midori and same error
<asheesh>
Interesting. What's the specific error?
<puck2>
server is definitely running and i can ssh into it (after installing openssh server)
<puck2>
midori says "ssl handshake failed"
<asheesh>
That's so weird.
<asheesh>
Would you be OK if you share the URL with me so I can test?
<asheesh>
I wonder if there's some deeper problem that you're running into.
jadewang has joined #sandstorm
mnutt_ has joined #sandstorm
<puck2>
ff says "secure connection failed"
<puck2>
pm ok?
<asheesh>
Sure!
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]