chore: update dev ports to avoid conflicts with fCC Proper#566
Merged
utsab merged 2 commits intofreeCodeCamp:mainfrom Jan 27, 2026
Merged
chore: update dev ports to avoid conflicts with fCC Proper#566utsab merged 2 commits intofreeCodeCamp:mainfrom
utsab merged 2 commits intofreeCodeCamp:mainfrom
Conversation
NewtonLC
previously requested changes
Dec 6, 2025
CarlyAThomas
force-pushed
the
chore/update-dev-ports
branch
from
d68ca85 to
6595fc0
Compare
Contributor
Author
|
I have added instructions for Auth0 in the readme with the corrected ports as well as updates for the environment files .env.sample and .codespace-instructions.sh. Per request, gitpod instructions and notation is being removed in another PR and thus .gitpod.yml has not been modified here see PR #573. |
Collaborator
|
Thanks @CarlyAThomas for factoring in my feedback form our last conversation to add documentation for setting up Classroom App on the same local machine as FCC Proper. |
utsab
approved these changes
Jan 27, 2026
- Change develop server port from 3000 to 3001 - Change mock-fcc-data port from 3001 to 3002 - This allows classroom to run alongside fCC Proper (ports 3000/8000)
- Update README.md with port information in setup steps - Update .env.sample with new NEXTAUTH_URL and mock data URL - Update codespace-instructions.sh with new port URLs - Update .devcontainer/devcontainer.json forwardPorts array These changes ensure documentation reflects the new port configuration that avoids conflicts with freeCodeCamp's main platform (ports 3000/8000).
CarlyAThomas
force-pushed
the
chore/update-dev-ports
branch
from
6595fc0 to
0c00699
Compare
CarlyAThomas
added a commit
to CarlyAThomas/classroom
that referenced
this pull request
Feb 2, 2026
…amp#566) * chore: update dev ports to avoid conflicts with fCC Proper - Change develop server port from 3000 to 3001 - Change mock-fcc-data port from 3001 to 3002 - This allows classroom to run alongside fCC Proper (ports 3000/8000) * docs: update port references from 3000/3001 to 3001/3002 - Update README.md with port information in setup steps - Update .env.sample with new NEXTAUTH_URL and mock data URL cd /home/arora/classroom && git status -sb cd /home/arora/classroom && GIT_EDITOR=true git rebase --continue - Update codespace-instructions.sh with new port URLs - Update .devcontainer/devcontainer.json forwardPorts array These changes ensure documentation reflects the new port configuration that avoids conflicts with freeCodeCamp's main platform (ports 3000/8000).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist:
Update index.md)Reason
This allows classroom to run alongside freeCodeCamp's main platform for integration testing. fCC Proper uses ports 3000 (backend) and 8000 (frontend), which conflicts with classroom's default port 3000.
Testing
✅ Verified npm run develop starts on port 3001
✅ Verified npm run mock-fcc-data starts on port 3002
✅ Confirmed no port conflicts when running both services simultaneously