ocdtrekkie has quit [Remote host closed the connection]
aldeka has quit [Remote host closed the connection]
aldeka has joined #sandstorm
ocdtrekkie has joined #sandstorm
paroneayea has quit [Read error: Connection reset by peer]
natea has quit [Quit: natea]
paroneayea has joined #sandstorm
natea has joined #sandstorm
gopar has quit [Quit: Leaving]
joshbuddy has quit [Quit: joshbuddy]
soulshake has joined #sandstorm
gopar has joined #sandstorm
bb010g has quit [Quit: Connection closed for inactivity]
aatkin has joined #sandstorm
<aatkin>
Just wondering if anyone could advise me on whether ipfs (specifically the webui) would be a good candidate for a sandstorm app. One of the porting problems would be that the background daemon communicates via DHT...so I'm not sure about how to handle that. Was hoping a single daemon could run in the background outside Sandbox and the grains would just be webui sessions all talking to the same daemon...
<aatkin>
...or maybe the daemon could run on another non sandstorm server and talk to webui via https...hmmm
rhapsodhy has quit [Remote host closed the connection]
rhapsodhy has joined #sandstorm
bb010g has joined #sandstorm
<kentonv>
aatkin: it sounds like Sandstorm will need an ipfs "driver" before it can support the webui as an app.
<kentonv>
unfortunately we're not ready for drivers just yet.
<kentonv>
(a driver is an app that has full network access, implements some network protocol, and then re-exports the protocol to other apps as a Cap'n Proto capability-based API)
aatkin has quit [Ping timeout: 246 seconds]
aatkin has joined #sandstorm
aatkin has quit [Ping timeout: 272 seconds]
aatkin has joined #sandstorm
paroneayea has quit [Read error: Connection reset by peer]
aatkin has quit [Quit: Leaving]
paroneayea has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
pixelport has joined #sandstorm
Isla_de_Muerte has joined #sandstorm
gopar has quit [Quit: Leaving]
jadewang has quit [Ping timeout: 272 seconds]
pixelport has quit [Ping timeout: 252 seconds]
NwS has quit [Ping timeout: 258 seconds]
pixelport has joined #sandstorm
<pixelport>
Do I have to invite a user to sandstorm to let them use libre board?
<pixelport>
I have a private board and I can't find any way to add a new member
rhapsodhy has quit [Ping timeout: 256 seconds]
rhapsodhy has joined #sandstorm
Isla_de_Muerte has quit [Ping timeout: 272 seconds]
<paulproteus>
mquandalle: ^
<paulproteus>
pixelport: Please meet mquandalle , one of the LibreBoard authors!
<paulproteus>
Stick around a few hours for .fr to get online. I'm going to sleep now myself.
<pixelport>
have to go now but will be back in a few hours
<paulproteus>
dosch: I'm glad you found your way on to IRC, and that you got your problem resolved, and that you tried out Sandcats!
<dosch>
paulproteus: yeah, went smooth. Sandcats seems nice.
<dosch>
I think so far the thing I miss in Sandstorm is nice URLS. Say I create an etherpad, or chatchannel and want to invite friends, I'd like to be able to spell out the url over phone.
<dosch>
So far sandstorm only seems to create urls for sharing that are very secure and unique and thus long...
<mquandalle>
but since I've done many changes, there is a serious amount of bugs in the current master branch
<mquandalle>
(and a few missing features)
<mquandalle>
that need to be fixed before releasing v0.9
<pixelport>
okay
<mquandalle>
Reading your previous message I just want to make it clear that v0.9 is not yet released
<pixelport>
Could a workaround be to set the bort to public and add a robot.txt for the server directory? But it seems like there is no easy way to edit this in sandstorm
<pixelport>
so it would not be found by google. The url seems long enugh that its hard to guess
<pixelport>
*enaugh
<pixelport>
*enough :)
<ocdtrekkie>
pixelport: For a decent amount of time, the primary security of Sandstorm was that nobody could guess the URL. :)
<ocdtrekkie>
The fact that the URL doesn't work for anyone who enters it by default is actually a very new feature for Sandstorm.
<pixelport>
does sandstorm anything that tells search engine bots that there is a libre board on this server?
<ocdtrekkie>
No, the URLs are unguessable for a reason.
<pixelport>
okay than I will go with this route
<ocdtrekkie>
By default, currently, you should be able to create Share links to your board in Sandstorm, if permissions haven't been enabled by LibreBoard yet (they haven't), anyone who uses the /shared link on your server has write access to that board.
<ocdtrekkie>
And as long as you don't post that shared link anywhere public, or give it to people who shouldn't have it, your board is private. (You can also revoke the shared link and access to anyone who shouldn't have it from the Share button.)
<pixelport>
ocdtrekkie: no this defietly doesn't work with board which are set to private
<pixelport>
the user can create a new account
<pixelport>
but cannot access the board and there is no way to give the user the rights to do so
<ocdtrekkie>
They can sign into Sandstorm, which will identify them when they visit a sharing link, but it doesn't let them create their own LibreBoards and such without an invite.
<ocdtrekkie>
If you've got a LibreBoard open in Sandstorm, you should have a blue Share button on the black bar at the top, yes?
<pixelport>
yes thats correct but when someone tries to register over this link the permissions aren't set
<ocdtrekkie>
So you gave someone a /shared/ link to your LibreBoard grain and they cannot create cards and such?
<pixelport>
yes when the board is private the user who registered over the shared link can not access the board in any way
<ocdtrekkie>
I'm kinda getting caught on what you mean by "registered". Signing into Sandstorm itself, right? What do they see if they click the /shared/ link?
<ocdtrekkie>
See if you can use it/create cards/etc.
<ocdtrekkie>
Oooooh, I see. Yeah, that's a LibreBoard 0.8 issue/bug, I would think.
<ocdtrekkie>
LibreBoard shouldn't ever show you a "sign up" or "log in" button on Sandstorm.
<ocdtrekkie>
Most Sandstorm apps allow write access by default if shared. I had to go into an incognito window to see what you were looking at.
<pixelport>
ocdtrekkie: this board is public. The problem only occurs when the board is set to private
<pixelport>
but I think this should be fixed in 0.9
<ocdtrekkie>
pixelport: A "public" board in Sandstorm, is still private, basically.
<pixelport>
In sandstorm this might be true
jadewang has joined #sandstorm
<ocdtrekkie>
This is basically just an issue because LibreBoard is designed to run outside of Sandstorm, so it has it's own public/private permissions and then Sandstorm has it's own shared/private permissions basically.
<ocdtrekkie>
So for you to share something using the Sandstorm options, it needs to be "public" in LibreBoard.
<pixelport>
you shouldn't need to invite users to sandstorm to let them access apps like libre board.
<pixelport>
the privacy settings are misleading
jadewang has quit [Ping timeout: 264 seconds]
<ocdtrekkie>
They don't need to be invited to Sandstorm, but they need a Sandstorm sharing link. LibreBoard having it's own public/private setting inside Sandstorm is a bit confusing (I was confused).
<ocdtrekkie>
Inviting to Sandstorm allows people to *create* new instances of apps (like new LibreBoards), but you do not need an invite to use them.
<pixelport>
ocdtrekkie: Its not working at all! How to reproduce: create new sandstorm.io demo. Install Libre board. Create new Board. Create with blue "Share" button a share Link. Open Share Link in new Incognito window. Register new Libre board account ("Sign up for free"). Error: "0 must be an object [400]". Try to login with new account. User cannot access boards: "No boards.". If you go back to the shared link the user is not
<pixelport>
logged in.
<dwrensha>
I suspect that this is a bug in the LibreBoard package
<dwrensha>
I remember seeing similar problems when I tried it out
<kentonv>
right, this is a bug in libreboard; it should not be asking you to "sign in" at all, because Sandstorm handles all login
<pixelport>
Is there already a github issue open?
<kentonv>
I'm not sure
<ocdtrekkie>
Well, mquandalle already said it'll be fixed in 0.9, which isn't ready for release yet.
<ocdtrekkie>
There's really no solution other than to wait for the app to get updated.
<pixelport>
ocdtrekkie: should I open a github issue then?
<kentonv>
you should report an issue against libreboard
<kentonv>
itscassa: currently the "invite users" page is actually a separate page form the admin panel and does not accept the token
<kentonv>
we're actually fixing this soon
* ocdtrekkie
is learning things
<itscassa>
How can I invite myself to access Sandstorm then?
<kentonv>
but for now you need to be logged in as the admin user to send invites
<kentonv>
the first user to log in becomes admin
<kentonv>
automatically
<itscassa>
Not in my case :/
<kentonv>
hmm
<itscassa>
Is there some way to reset that?
<kentonv>
did you by any chance attempt email login first, have it not work (due to SMTP configuration), and then attempt a different login mechanism subsequently?
<itscassa>
Ah, yes
<kentonv>
heh... yeah so the email you tried to log in with is admin, but you can't use it. :(
<itscassa>
Yep
<kentonv>
someone reported the same problem yesterday
mort___ has quit [Quit: Leaving.]
<kentonv>
we will also have this fixed soon, by introducing a user management panel where you can assign admin rights
<itscassa>
Is there a way to reset it other than reinstalling sandstorm?
<kentonv>
there are two options
<kentonv>
one is, use "sudo sandstorm mongo" to get to the mongo shell and manually add "isAdmin: true" to your user entry in db.users
<kentonv>
I tried to talk someone through this yesterday but didn't succeed
<kentonv>
so maybe only do that if you are familiar with mongo already
<kentonv>
otherwise, the other option is to delete the mongo DB and start over, that is:
<kentonv>
sudo rm -rf /opt/sandstorm/var/mongo/*
<kentonv>
err
<kentonv>
first: sudo sandstorm stop
<kentonv>
:)
<kentonv>
and then after deleting: sudo sandstorm start
<kentonv>
and to get a new token: sudo sandstorm admin-token
<itscassa>
db.users.find(): error: { "$err" : "not authorized for query on sandstorm.users", "code" : 16550 }
<kentonv>
that's weird
<itscassa>
Wait
<itscassa>
I'm logged in as the user sandstorm :p
<itscassa>
Or, su'ed
<kentonv>
use "sudo sandstorm mongo" to connect, it should authenticate you correctly
<kentonv>
or if you installed sandstorm non-root, I guess you have to su to sandstorm and then do "sandstorm mongo"
<kentonv>
interesting, maybe we should auto-detect that problem
<itscassa>
Nope :-(
<kentonv>
hmm normally the greeting is actually sent to the client before the client says anything
<kentonv>
so it sounds like your SMTP server is accepting the connection then remaining silent
<kentonv>
that is, if the error message is correct, which of course it might not be
<kentonv>
try telnetting to it and see what you get back?
<itscassa>
telnetting works
<itscassa>
And other mailing clients work
<jparyani>
itscassa: are you setting the smtp url in the admin settings page or in sandstorm.conf?
<itscassa>
Admin settings page
<itscassa>
What's the key for sandstorm.conf SMTP?
<itscassa>
Nvm :P
<itscassa>
Hmm dang
<itscassa>
Setting it broke the instance XD
<jparyani>
i was worried about a confusing interaction in that the admin settings page takes precedence over the sandstorm.conf setting. I don't think that's your problem though
<itscassa>
Nvm, permissions errors
<itscassa>
Let's check again
<itscassa>
Hmm nope
<jeffmendoza>
I'm going through the porting guide with a sample app, how do you tell spk to pack up mysql with your app?
bb010g has quit []
bb010g has joined #sandstorm
<kentonv>
jeffmendoza: well, the first step is to have a start script that starts mysql and then your app
<kentonv>
and have that be your start command
<jeffmendoza>
ah I See
<kentonv>
jparyani can help with details
<kentonv>
note that if you can use sqlite, it's probably better than mysql on Sandstorm
<jeffmendoza>
right
<itscassa>
Who's the builder of Paperworks
<itscassa>
Or what's the repo
<kentonv>
itscassa: should be linked from the app list
<itscassa>
Ah forgot that
<jeffmendoza>
it's ironic, most people are trying to scale out, sandstorm apps are the opposite
<kentonv>
indeed. :)
<kentonv>
sandstorm is targeted at the individual user or internal business apps
<kentonv>
not SaaS
<kentonv>
also we try to do things like one-document-per-instance, which makes instances really small even if there are lots of documents
<kentonv>
this actually makes apps a lot easier to develop; no need to implement document management, access control, etc.
<jeffmendoza>
=)
<kentonv>
and it means that an individual instance has no need to scale out
<kentonv>
Sandstorm can easily scale out by load-balancing instances across worker machines. (This is what Blackrock, our enterprise product, will do.)
<jparyani>
itscassa: what version of sandstorm are you running? you can check by running `sandstorm --version` on the command line, or viewing the home page of your sandstorm instance when not logged in
<itscassa>
jparyani: 81
itscassa is now known as itscassa|away
paroneayea has quit [Read error: Connection reset by peer]