Supabase Infrastructure setup guidance
Hello all,
(Sorry in advance, kind of lengthy). If this has already been asked and answered, my apologies, please provide a link to answers and I will self-study.
I'm looking to use Auth exclusively for now (kind of a little old school when it comes to relinquishing "control" of my data - maybe I'll get there one day).
Anyway, on the free plan for now and looking for some help in thinking about correctly using Auth for my product's needs.
The free plan says it allows 2 organizations - what exactly is meant by "organization"? Then, each organization has "projects". How are they different/the same and how should they be used?
The problem(s) I am trying to solve:
1 - I'm going to need 3 environments (do I handle this with organizations or projects?:
(Sorry in advance, kind of lengthy). If this has already been asked and answered, my apologies, please provide a link to answers and I will self-study.
I'm looking to use Auth exclusively for now (kind of a little old school when it comes to relinquishing "control" of my data - maybe I'll get there one day).
Anyway, on the free plan for now and looking for some help in thinking about correctly using Auth for my product's needs.
The free plan says it allows 2 organizations - what exactly is meant by "organization"? Then, each organization has "projects". How are they different/the same and how should they be used?
The problem(s) I am trying to solve:
1 - I'm going to need 3 environments (do I handle this with organizations or projects?:
- Local dev
- Stage/test
- Production
2 - Each of my clients will access the system via a sub-domain (clientA.mysystem.com and clientB.mysystem.com). Ideally, if an employee of a client were to move to another client using my system (person moves from clientA to clientB) I'd like them to be able to signup using their same username (john.doe) and email (john.doe@gmail.com) in both places. Would that be by separating clients by organization or project or ?
