-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
How to keep Parse Dashboard Live All the time #3095
Comments
Run this from the dashboard root folder.
|
what about the config file parse-dashboard --config parse-dashboard-config.json --allowInsecureHTTP=1 i am running through this command can u help me in this |
@Heman6886 You can run that in a separate file then run that using PM2. Eg save this to a file called ecosystem.json
Then inside config parse-dashboard-config.json you set all your values. Then you can |
Where does the ecosystem.json lies |
Just create it and place that code in there. Then save it in your home or directory you currently have that other config file. Then use pm2 to start! |
@Heman6886 Next time you create a issue, please clear out or fill in the provided template first. For example, there is no instructions for us to follow for your "issue". It's just a question. Even if you copy the title of the issue, "How to keep Parse Dashboard Alive", that is much cleaner than the template markdown that you neglected to remove. Thanks |
I'm going through open issues and cleaning things up a bit. Parse Dashboard has its own repo, lets keep Dashboard discussion out of Parse Server issues. Thanks! |
Please read the following instructions carefully.
Check out #1271 for an ideal bug report.
The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
Many members of the community use Stack Overflow and Server Fault to ask questions.
Read through the existing questions or ask your own!
For database migration help, please file a bug report at https://parse.com/help#report
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
You've met the prerequisites: https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites.
You're running the latest version of Parse Server: https://github.com/ParsePlatform/parse-server/releases
You've searched through existing issues: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue Chances are that your issue has been reported or resolved before.
You have filled out every section below. Issues without sufficient information are more likely to be closed.
--
Issue Description
[DELETE EVERYTHING ABOVE THIS LINE BEFORE SUBMITTING YOUR ISSUE]
Describe your issue in as much detail as possible.
[FILL THIS OUT]
Steps to reproduce
Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.
Expected Results
[FILL THIS OUT]
Actual Outcome
[FILL THIS OUT]
Environment Setup
Server
Database
Logs/Trace
You can turn on additional logging by configuring VERBOSE=1 in your environment.
[FILL THIS OUT]
The text was updated successfully, but these errors were encountered: