How to access non-public sprite URLs?

[ryang]

Has anyone had success with non-public sprite URLs? I can’t tell if they’re not working or if I’m doing something wrong.

Create sprite, run server on 8080:

sprite create       
┃ Name your sprite
✓ Created swift-amber-phoenix sprite in 0.4s
...
● Connecting to console...

sprite@sprite:~# python3 -m http.server 8080
Serving HTTP on 0.0.0.0 port 8080 (http://0.0.0.0:8080/) ...

Get a URL:

$ sprite url -s swift-amber-phoenix
URL: https://swift-amber-phoenix-blhdr.sprites.app
Auth: sprite

But when I go to https://swift-amber-phoenix-blhdr.sprites.app/ I get {"error":"unauthorized"}

At the root sprites.app I see the option to Sign In, but it redirects me to sprites.dev and the state on .app doesn’t seem to be connected to sign in on .dev.

Are sprite URLs not meant to be accessed in the browser in this way? Am I doing something wrong/unexpected? Or is this just work in progress? (Public URLs do work)

Very cool product–the go SDK is quite nice and I’m excited to see what else you do with sprites.

[eli]

thanks for calling this out! I’ll ask around to see if there’s a better way I’m overlooking, but I’ve always just used my sprite token when I need to make a request to a private URL, eg: curl -H "Authorization: Bearer $SPRITE" <sprite-url>.

[ryang]

That’s helpful, thanks @eli! I was thinking that authentication was done via your signed-in account, but being able to curl with the bearer token works great.

I noticed the filesystem additions to the golang SDK earlier today so I know the team is adding stuff at a rapid pace.