Skip to content
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

Closed
4 tasks
HemanParbhakar opened this issue Nov 22, 2016 · 8 comments
Closed
4 tasks

How to keep Parse Dashboard Live All the time #3095

HemanParbhakar opened this issue Nov 22, 2016 · 8 comments

Comments

@HemanParbhakar
Copy link

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!

--

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.

  1. [FILL THIS OUT]
  2. [FILL THIS OUT]
  3. [FILL THIS OUT]

Expected Results

[FILL THIS OUT]

Actual Outcome

[FILL THIS OUT]

Environment Setup

  • Server

    • parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
    • Operating System: [FILL THIS OUT]
    • Hardware: [FILL THIS OUT]
    • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
  • Database

    • MongoDB version: [FILL THIS OUT]
    • Storage engine: [FILL THIS OUT]
    • Hardware: [FILL THIS OUT]
    • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): [FILL THIS OUT]

Logs/Trace

You can turn on additional logging by configuring VERBOSE=1 in your environment.

[FILL THIS OUT]

@HemanParbhakar HemanParbhakar changed the title How to keep Parse Live All the time How to keep Parse Dashboard Live All the time Nov 22, 2016
@srameshr
Copy link
Contributor

Run this from the dashboard root folder.

pm2 start ./Parse-Dashboard/index.js

@HemanParbhakar
Copy link
Author

HemanParbhakar commented Nov 22, 2016

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

@Cliffordwh
Copy link

@Heman6886

You can run that in a separate file then run that using PM2.

Eg save this to a file called ecosystem.json

{
"apps" : [{
    "name"        : "parse-dash",
    "script"      : "/usr/bin/parse-dashboard",
    "watch"       : true,
    "merge_logs"  : true,
    "cwd"         : "/home/parse",
    "args"         : "--config parse-dashboard-config.json"
  }]
}

Then inside config parse-dashboard-config.json you set all your values.

Then you can PM2 start ecosystem.json
PM2 save

@HemanParbhakar
Copy link
Author

Where does the ecosystem.json lies

@Cliffordwh
Copy link

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!

@OneCricketeer
Copy link

@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

@hramos
Copy link
Contributor

hramos commented Nov 29, 2016

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!

@hramos hramos closed this as completed Nov 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants