-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REDASH_MULTI_ORG broken in Angular 1.5 #1447
Comments
Any file under
The send_static handler is also not called despite it having the route Files under |
Adding specific routes for the files in
Redash however, does not load properly. |
The multi tenancy support is not officially supported or documented as it is something I introduced as provisioning for the hosted version. This is why I felt comfortable breaking it in the webpack branch until I will have the time to fix it. There are two issues here:
Some options:
I like option #2 or #4. The subdomain option is probably the best, but might take time to migrate so prefer "to_parse". |
@adamlwgriffiths did you look into it more? |
I haven't had the time to look any further into this.
… On 24 Dec 2016, at 3:27 am, Arik Fraimovich ***@***.***> wrote:
@adamlwgriffiths did you looked into it more?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
As per your comment above, there may also be a way to set the base url during the asset build stage? Are there any plans to take a look at this? |
No, because the base URL depends on the current org_slug, so it's something that needs to be done in runtime.
Yes. |
Finally I got around to looking at this again and I had this thought: what if we drop I feel like the |
I'm not really fussed. |
For sure it won't be indefinitely -- I need this too :) I just didn't want to block the 1.0 release with it. |
I merged the branch that supposed to fix this. It seems to be working properly. It has a different workflow for development than the single tenant one (you can't use webpack-dev-server with it). I still want to review all APIs to make sure that in the migration to SQLAlchemy we didn't break multi-tenancy protection anywhere... |
The latest code in master no longer works with
REDASH_MULTI_ORG=True
.What I can gleam is that the asset requests are being thought to be an organization (http://host/app.js -> http://host/org where org: app.js).
I think there may have been some logic for this in the template previously, but it's been lost.
The output is as follows (I've added a print for the
SLUG = X
inauthentication/org_resolving.py
):The text was updated successfully, but these errors were encountered: