Sandbox vs Beta vs Production?

624 views
Skip to first unread message

Kevin

unread,
Dec 17, 2013, 12:48:41 AM12/17/13
to feedly...@googlegroups.com
Looking to understand how these three environments are connected and which one (beta or sandbox) to test against.  I would think beta is where you try things, sandbox is where you mirror production for devs to test against and production is, well, production.

I understand that the sandbox and production have the same developer secret IDs and URI redirects in them, does beta also?

If so, is it okay to test our apps against beta?

How will the new Google authentication you are trying in beta change the (auth) APIs?

Last question based on…

"If there are no issues reported by the end of the week, we will promote 17.7 to the main channel over the [weekend]."

Any chance this will effect our apps from authenticating properly - or break the current access-token auth??  Apple has a shut down on app updates on Dec 21st to the 27th.  It would not be good for our app users to get our apps and then have an authentication issue.  We wouldn't be able to even submit an app update until the 27th.

Thanks for your time
Kevin



Edwin Khodabakchian

unread,
Dec 17, 2013, 1:56:09 AM12/17/13
to Kevin, feedly...@googlegroups.com
Hi Kevin,

Beta is a feedly UI concept. It is something that allows up to test the feedly web UI before it goes to production. The backend of beta is production cloud. As such it is not possible for us to share beta with other developers. Sandbox is what we use to beta the back end.

-Edwin

--
You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.
To post to this group, send email to feedly...@googlegroups.com.
Visit this group at http://groups.google.com/group/feedly-cloud.
To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/2797bfd8-d1d5-4f91-9312-b6fb2aaf7eba%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Kevin

unread,
Dec 17, 2013, 2:13:09 AM12/17/13
to feedly...@googlegroups.com, Kevin, edw...@devhd.com
Thank you.  I now understand beta better.  So, let's move on to Sandbox…

If sandbox is the backend - what is the sandboxes UI (front end)?  Is the auth update (17.7) you just applied to beta also on the UI for the sandbox?  I'm sorry if I have this totally wrong.

I guess what I'm really getting at is will the Authentication API steps…
  1. Authenticating a user and obtaining a code
  2. Handling the response (the redirect URI etc)
  3. Exchanging a code for a refresh token and an access token
  4. Using a refresh token
…change at all with the new auth you are putting in place as soon as this weekend?

Or will the current access tokens continue to work after the 17.7 change goes to the production channel?

Thank you for your (late night) time
Kevin

Edwin Khodabakchian

unread,
Dec 17, 2013, 2:17:39 AM12/17/13
to Kevin, feedly...@googlegroups.com
We have a feedly UI for the sandbox. You can access it on http://sandbox.feedly.com developers sometimes use that UI to see their feedly account with some feeds.

The Auth changes we are performing will be 100% transparent to developers. Developers will continue to authenticate against the feedly API and receive the feedly token. Behind the scene, feedly will delegate to the new google sign in.

-Edwin
Reply all
Reply to author
Forward
0 new messages