Repository navigation
Parse Dashboard requires active internet connection #2009
Description
After a fresh installation of Parse Dashboard it wont run if Im not connected to the internet.
I am in a place where I do not have access to internet , and I am trying to work offline.
Everytime I connect to the internet it works just fine, but when I dont have have internet,,,nothing
Here is the Command I am using
parse-dashboard --appId yourAppId --masterKey yourMasterKey --serverURL "https://localhost:1337/parse" --appName myapp
Activity
parse-github-assistant commentedon Jan 22, 2022
Thanks for opening this issue!
mtrezza commentedon Jan 22, 2022
Could you describe how you intend to "work offline" with Parse Dashboard? Using the issue template as required could help others better understand your request.
[-]Server wont start unless connected to the Internet[/-][+]Parse Dashboard requires active internet connection[/+]Codzaa commentedon Jan 23, 2022
@mtrezza Thanks for replying.
I just simply want to run parse dashboard on my local machine without internet access.
Here is the error I'm getting if my machine is does not have internet connection
After connecting to the internet it works.
Is there some configurations I have to edit for this to work?
damianstasik commentedon Jan 23, 2022
It is caused by the mechanism that checks if there are any updates. We could add a
catchblock that assigns an empty arrray to thenewFeaturesInLatestVersionvariable if there were any errors. This should also handle other types of errors like npm registry being unavailable due to downtime etc.What do you think @mtrezza?
mtrezza commentedon Jan 23, 2022
I see, that's the feature that has been fixed / reactivated recently. Yes, I think this should just silently and gracefully fail if it can't retrieve any data, for whatever reason. It's more of a non-essential "marketing" feature.
Codzaa commentedon Jan 23, 2022
@visualfanatic @mtrezza So is there a work around or some hacky stuff I can do to get to work for now?
damianstasik commentedon Jan 23, 2022
@mtrezza @Codzaa Here is PR with the change: #2015
mtrezza commentedon Jan 23, 2022
Closing via #2015.
Released in 4.0.0-alpha.14.