@@tnc1997 Thank you for your replay , one more thing can be related also to your multitenancy video, how to handle the multi-tenancy application when you are using the header strategy and the user will use a unified login page.
@@tnc1997 Assuming you have a multi-tenant system using multiple databases, during user login, the system cannot yet determine the user's tenant. To handle this, a central database or identity server is required to verify the user's credentials. Once verified, the system can redirect the user to the appropriate tenant database. Additionally, Finbuckle's WithHeaderStrategy can be used as an alternative to the host strategy for tenant identification, allowing tenant information to be passed through HTTP headers Thank you again for your replay and i cannot wait to see your video about that :)
Would you please make a video about DBUp for data seeding and how to use it within Docker Compose?
Thank you very much for the suggestion, it is a video that I will consider in the future.
@@tnc1997 Thank you for your replay , one more thing can be related also to your multitenancy video, how to handle the multi-tenancy application when you are using the header strategy and the user will use a unified login page.
Could you expand on what you are trying to accomplish with the header strategy and a unified login page to help me plan a video in the future?
@@tnc1997 Assuming you have a multi-tenant system using multiple databases, during user login, the system cannot yet determine the user's tenant. To handle this, a central database or identity server is required to verify the user's credentials. Once verified, the system can redirect the user to the appropriate tenant database. Additionally, Finbuckle's WithHeaderStrategy can be used as an alternative to the host strategy for tenant identification, allowing tenant information to be passed through HTTP headers
Thank you again for your replay and i cannot wait to see your video about that :)