Serving behind a proxy #93
badarsebard
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
Hail, @badarsebard 👋 Welcome to Fief's kingdom! Our team will get back to you very soon to help. In the meantime, take a minute to star our repository ⭐️ Farewell! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @badarsebard 👋 Handling arbitrary path prefix would be quite difficult with our current implementation since the prefix is used for Tenants: you can have several tenants in one workspace:
There are also lot of difficulties with URL generation. Currently, I don't really see how it would be possible without breaking everything 🤔 |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using fief for a kubernetes application and would like to serve it behind an nginx proxy. There are two issues with this: first the use of subdomains for the workspaces and second the app can't currently be served from a URL prefix. It would be ideal if I could host the fief application under a single domain and URL prefix like
mydomain.local/fief/
.As far as implementation the FastAPI app can take and argument
root_path
that serves all endpoints under a prefix. The react app will need something more dynamic since if I understand correctly it builds during the pypi package install. These would take care of serving under a URL prefix. I have no idea about the subdomains though. Would it be possible to fold the workspaces into the URL structure. For instancedomain.org/{workspace}/admin/
Beta Was this translation helpful? Give feedback.
All reactions