30 ms·
Awh man is this cool! I had a similar idea kicking around for a while (for a different market) because you end up managing disparate targets (including multipl
by devbug 11y ago
Awh man is this cool!
I had a similar idea kicking around for a while (for a different market) because you end up managing disparate targets (including multiple digital distributors for one platform) each with their own slightly broken of doing things. It. Sucks. Hard.
Now that I'm only tangentially involved with the market my previous experience (of intense pain) is reduced, but has been replaced with iOS and Android.
I'm looking forward to using BuddyBuild for the next app I work on.
How are you handling the Apple side of things? Last I checked, you had to store full credentials to someone's Apple ID. Looks like you are doing exactly that.
My big concern is that you're siloing my credentials so they won't get leaked. How are you doing that?
- chrisstott 11y agoWe take this very seriously. At a high level, our front end servers can write credentials, but never read them. Only the build machines (which are isolated from the public internet) can decrypt and use them... and only for a short duration during a build. A good portion of our infrastructure is built on AWS - where a majority of our team had worked to build services with similar secure environments.