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

Dynamically adding applications and users #386

Closed
2 tasks done
koritze opened this issue May 31, 2016 · 3 comments
Closed
2 tasks done

Dynamically adding applications and users #386

koritze opened this issue May 31, 2016 · 3 comments
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@koritze
Copy link

koritze commented May 31, 2016

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

  • You're running version >=2.1.4 of Parse Server.
  • You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Hi,
I am trying to run Parse in Openshift environment.

My current architecture:

  • Parse-Dashboard container will mount a volume (shared storage) that contains all the Parse-Servers in JSON.
  • Parse-Server container - all arguments will be supplied via environment variables - Stateless.
  • Mongo - replica set.

I would like to use the same dashboard for multiple parse-servers which represents different applications.
In the current implementation of Parse-dashboard a major limitation exists - a restart is needed for every addition of parse-server.
The obvious solution is to hold the configuration data in a database, but the disadvantage is the binding of the parse-dashboard to the database.

After the change is made it will be easy to add a management console to the Parse-Dashboard server, to allow easy and fast creation of users, applications and assignment of administrators.
For example, adding new application:
Parse-dashboard:Create new application > Parse-dashboard:Generates MASTER_KEY > Openshift:Create parse-server with the MASTER_KEY > Parse-dashboard:Insert the rest of the parameters of the app (serverURL, etc)

I'm opening this issue to start a discussion.

@koritze koritze changed the title Dynamically adding applications and users Dynamically adding applications and users [enhancement] May 31, 2016
@koritze koritze changed the title Dynamically adding applications and users [enhancement] Dynamically adding applications and users May 31, 2016
@koritze koritze changed the title Dynamically adding applications and users Dynamically adding applications and users @enhancement May 31, 2016
@koritze koritze changed the title Dynamically adding applications and users @enhancement Dynamically adding applications and users #enhancement May 31, 2016
@koritze koritze changed the title Dynamically adding applications and users #enhancement Dynamically adding applications and users May 31, 2016
@drew-gross
Copy link
Contributor

Sounds useful, also potentially related #188. A real database might be overkill, and would add a pretty huge dependency to Parse Dashboard. My suggestion would be to add an endpoint to the express app that serves the dashboard that just writes to the config file. I'm open to other ideas though.

@grassland-curing-cfa
Copy link

I have been trying to migrate my Parse.com hosted app to the architecture of Heroku + mlab (both with free quota).

I am also interested to have the function of Create a New App on the Dashboard. After the Parse hosted service is shut down end of Jan 2017, I think it'd be very troublesome to create a new Parse app on my current architecture as I am still trying to figure out a best practice to create a new Parse app with Heroku + mlab. My idea is:

  1. Create an empty MongoDB instance running on mlab, and get the URI to it;
  2. Deploy the Parse-example to Heroku as a Heroku app;
  3. Configure the config. variable the Heroku app to point to the MongoDB URI;
  4. Add the Heroku app to the configuration file of the Parse-dashboard;
  5. Add new classes and rows via the Parse-dashboard.

Please let me know what you think about the steps as above.

@stale
Copy link

stale bot commented Jan 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Jan 11, 2019
@stale stale bot closed this as completed Jan 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

3 participants