Skip to content

/ docs

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

Jump to bottom

📙 Parse Depolyement for Glitch needs to be updated #704

Open
superboss224 opened this issue Jan 31, 2020 · 3 comments
Open

📙 Parse Depolyement for Glitch needs to be updated #704

superboss224 opened this issue Jan 31, 2020 · 3 comments
Labels
Documentation Improvement Parse Server Guide

Comments

@superboss224
Copy link

@superboss224 superboss224 commented Jan 31, 2020

Hello,
mLab no longer exists,
so this tutorial needs to be updated:
https://github.com/parse-community/docs/blob/gh-pages/_includes/parse-server/deploying-glitch-mlab.md
And about the bug, when remixing the Parse Glitch project, you can't use a MongoDB URI Connection String from MongoDB Atlas (free cluster) because an error says "DATABASE_URI not specified, falling back to localhost.".
It seems that the MongoDB Atlas Connection String is considered as invalid, it would be nice if someone would fix this doc and glitch project with something working in 2020 !
@superboss224 superboss224 added the Bug label Jan 31, 2020
@TomWFox
Copy link
Member

@TomWFox TomWFox commented Jan 31, 2020

@AngeloStavrow - any chance you could take a look at this?
@AngeloStavrow
Copy link
Contributor

@AngeloStavrow AngeloStavrow commented Feb 1, 2020 •
edited

Sure, I'll take a look. I imagine that the Heroku guide will also need to be updated by someone with knowledge of that platform for the same reason — not because Glitch or Heroic are the issue, but because mLab went away.

@TomWFox is there a preferred MongoDB provider to use for both? Atlas seems like the best candidate here but I imagine you all would prefer some consistency across the documentation. 🙂
@TomWFox
Copy link
Member

@TomWFox TomWFox commented Feb 1, 2020

Thanks, good point.

I would think Atlas would be the appropriate choice for both. Unless anyone has other ideas - @dplewis @acinader @davimacedo.
@TomWFox TomWFox changed the title 🐛 Parse Depolyement for Glitch needs to be updated 📙 Parse Depolyement for Glitch needs to be updated Jun 18, 2020
@TomWFox TomWFox mentioned this issue Sep 10, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Documentation Improvement Parse Server Guide
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@AngeloStavrow @TomWFox @superboss224