Parse init

[flovilmart]

A potential solution for our getting started problems...

Letting anyone create a server with npx @parse/init.

Potentially then we could add

npx @parse/init --dashboard

What do you guys think?

The goal is to promote best practices as well as properly configuring the server.

[acinader]

will look at again, and think about your question (i.e. what do you think). Off the cuff, looks pretty cool.

For the docker example, would be good if the example included some way to get cloud/main.js?

[flovilmart]

For the docker example, would be good if the example included some way to get cloud/main.js?

Yeah, but getting started with Docker is not the same as getting started with parse-server through npx.

This is why this README / onboarding is so confusing. We have zillions of ways to get started. Now the easiest way to get a server started in minutes (given you have node and mongo) is through npx.

THe second would be the docker one. Perhaps we should consolidate it all in the docs repo, but we need some good onboarding (if we care about onboarding) :)

[codecov]

Codecov Report

Merging #4960 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4960      +/-   ##
==========================================
- Coverage   93.75%   93.68%   -0.07%     
==========================================
  Files         123      123              
  Lines        8884     8884              
==========================================
- Hits         8329     8323       -6     
- Misses        555      561       +6

Impacted Files	Coverage Δ
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	91.52% <0%> (-0.73%)	⬇️
src/RestWrite.js	92.77% <0%> (-0.38%)	⬇️
...dapters/Storage/Postgres/PostgresStorageAdapter.js	97.08% <0%> (-0.09%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8dff708...54cd081. Read the comment docs.

[acinader]

I took a crack at using docker, but couldn't find a good solution for the cloud code, so I quickly ditched using Docker for deploying parse. There may well have been an easy, elegant solution, but I didn't come up with it or find it in the docs.

I have a "start" script in my package.json that is this simple: "start": "parse-server ./config.json",

So, either someone should figure out how we would use docker and cloud code and document that, or we should remove it from the docs.

I care about onboarding, and obviously, you do too.

[flovilmart]

Yeah, for docker actually, I would do a —docker options that creates a base docker file, and still is configured through env variables :)

[flovilmart]

It’s still a WIP. Let’s think about how we can make something cool for v4.0

[omairvaiyani]

Are there any frameworks you're looking for inspiration from in order to guide a default folding structure for parse server apps.. Ie generated on init?

[flovilmart]

Nothing in particular, but it’s inspired by many things out there. Trying to balance out the necessity of external dependencies, and ease of use, correctness and flexibility in the confits so they can evolve with your project etc...

[stale]

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.

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.