You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
Hi, I really like the suggested structure of your flas applications... I'm really new to Flask and to the freedom it provides. If you fin the time, can you answer a question?
I'm creating a multi-tenant application using the PostgreSQL schemas, where I will have a public schema + a schema for each tenant. So, I need my application to be something like this: http://www.application.com/tenant/
The problem is that I do not know how to best acommodate this in the overholt architecture. Could you give me some tips?
Thank you very much
The text was updated successfully, but these errors were encountered:
DanielFerreiraJorge
changed the title
Implementinf Application Dispatching by Path/Subdomain
Implementing Application Dispatching by Path/Subdomain
Apr 14, 2014
Hi, I really like the suggested structure of your flas applications... I'm really new to Flask and to the freedom it provides. If you fin the time, can you answer a question?
I'm creating a multi-tenant application using the PostgreSQL schemas, where I will have a public schema + a schema for each tenant. So, I need my application to be something like this: http://www.application.com/tenant/
I'm pretty sure the answer to achieve that is something like this: http://flask.pocoo.org/docs/patterns/appdispatch/#dispatch-by-path
The problem is that I do not know how to best acommodate this in the overholt architecture. Could you give me some tips?
Thank you very much
The text was updated successfully, but these errors were encountered: