-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
⚡ adds ability to run the dashboard from any mount point #217
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
Conversation
flovilmart
commented
Apr 1, 2016
- fixes allowInsecureHTTP
- fixes allowInsecureHTTP
@@ -83,7 +83,28 @@ module.exports = function(config) { | |||
|
|||
// For every other request, go to index.html. Let client-side handle the rest. | |||
app.get('/*', function(req, res) { | |||
res.sendFile(__dirname + '/index.html'); | |||
let url = req.url; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
infer the mount path
By analyzing the blame information on this pull request, we identified @drew-gross, @flovilmart and @gimdongwoo to be potential reviewers. |
Appreciate you looking into this! Good stuff, definitely less intrusive. I like how you inferred the mount path. A few issues that you might want to test:
|
You're free to test! |
Turns out the images in the push page don't work. Otherwise this looks sweet though. |
Yep, also the internal API, need to inject dashboardURL into the config.apps to minimize the footprint on the lib |
How would you feel about just injecting the config into the page directly? Then an extra fetch would not be necessary. Also, if you are moving the index.html into the source, can you also delete the actual index.html file? |
Yeah I was thinking about that too. also the scss loader is getting crazy with the relative image URL paths.... |
Ah, that is unfortuanate :( |
no I'm getting through it! |
Just noticed the favicon is missing too. Obviously that is lower-pri :p |
@flovilmart updated the pull request. |
Just remains the internal API calls in lib/ParseApp.js |
@flovilmart updated the pull request. |
7c75d16
to
678940e
Compare
678940e
to
eb09de5
Compare
@drew-gross that should be it! |
@flovilmart updated the pull request. |
// abortable flag used to pass xhr reference so user can abort accordingly | ||
export function request(method, url, body, abortable = false, withCredentials = true, useRequestedWith = true) { | ||
if (!url.startsWith('http://') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
open to suggestions about that, that's the less invasive I've found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is fine. The only things that aren't going to go through the Parse sdk are the config loading, and potentially this app creation stuff that is being discussed.
@flovilmart great job with this PR! With this, will we now be allowed to deploy the dashboard to Heroku? If so, how could I go about that? Do I need to set any specific environment/config variables? |
🎉 This change has been released in version 4.0.0-beta.1 |
🎉 This change has been released in version 4.0.0 |