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

Example config expects Parse Server on port 1338 instead of 1337 #2013

Closed
4 tasks done
mtrezza opened this issue Jan 23, 2022 · 1 comment · Fixed by #2012
Closed
4 tasks done

Example config expects Parse Server on port 1338 instead of 1337 #2013

mtrezza opened this issue Jan 23, 2022 · 1 comment · Fixed by #2012
Labels
type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Jan 23, 2022

New Issue Checklist

Issue Description

The Parse Server port in the dashboard example config file is 1338 which is different from the Parse Server default port 1337.

Steps to reproduce

n/a

Actual Outcome

Dashboard talks to port 1338 in the example config.

Expected Outcome

Dashboard should expect parse sever on port 1337.

Environment

Dashboard

  • Parse Dashboard version: 4.0.0-alpha.11
@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:feature New feature or improvement of existing feature label Jan 23, 2022
@mtrezza mtrezza linked a pull request Jan 23, 2022 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant