design multi-user support

[woolfg]

How can we separate users?

• the user can have multiple podcasts
• the user should be able to access data of other podcasts
• the user shouldn't be limited in metabase by any means

the separation can be done on two sides:

• stack itself (metabase, etc)
• database

[woolfg]

some cinsiderations:

• database separation can be done on db level (each user has its own db-schema) or on stack level (every user has its own db process)

• can metabase do a proper separation on user level or is it easier to just setup an instance per user?

• the DB should be that big as every podcast has exactlythe same amount of data. it just grown with the number of episodes and days => maybe we do a rough calc about the growth, current DB size is 23.078 MB in planetscale. I doubt that one podcast requires more than 500MB on long term, so should be a huge deal.

my first quick assessment leans towards a stack based separation which would spin up a new stack for every customer. this would simplify the permission handling, supports multi user support for a costumer (one customer can have unlimited user account in e.g. metabase, etc.)

[woolfg]

for now we create a new stack for a client. apple-automation is centralized.