OneToMany

On the recommendation of @louisbarclay from Cloakist, We now have live chat available!

We've gone with Chatwoot based on the simplicity of integration, the personal recommendation, and finally; a very helpful article for Live Chat options out there

Can't wait to talk to you all soon!

As a dev, I didn't think there was anything more exhilarating at the beginning of a project than plugging in your API to your database.

Turns out I'm definitely wrong! Seeing this Auth panel come to life for OneToMany is so satisfying! Had to share it here!

With this post, we mark the end of the 'dark-days' on IndieHackers. Everything that doesn't have a glamorous front-end has been nailed out including:

• Hosted API with custom domain
• DNS routing
• Initial Server configuration

🎉 Thanks for staying in the loop! 🎉

The Idea has a piece of the internet!

So many accounts are built around a one-to-one relationship. In my case, we had an apple account at work that suddenly required MFA. Non-negotiable.

The problem was, this account had been treated as a one-to-many account. Both myself, the US and the UK team had access to this account. All of a sudden only I had access to the MFA code and it was my responsibility to share the code, even at 2 am.

Despite trying to, removing the MFA was impossible, the only option was to add multiple other numbers.

So now we have one apple account we use for development, that has multiple trusted mobile numbers on it, all of which get MFA codes.

---

But that's just my problem, there are other use cases:

• Logging into GoDaddy for billing purposes
• Developer account sharing
• Account sharing with contractors, think Mailchimp