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

chore: use a new port if existing port is in use #199

Merged
merged 4 commits into from Jul 31, 2021

Conversation

rahulrana95
Copy link
Contributor

Currently we are using by default 3000 port.
So if that port is being used it will not throw error or open anything else.
Added a new library so it will search if 3000 not available then open new port in browser.

@imrajdas
Copy link
Contributor

imrajdas commented Jun 30, 2021

Good one for local development. But if it is running within a container/k8s, then it won't be required.

@rahulrana95
Copy link
Contributor Author

Good one for local development. But if it is running within a container/k8s, then it won't be required.

yeah agree

frontend/package.json Outdated Show resolved Hide resolved
@jyash97 jyash97 changed the title BugFix:Open a new port on local dev server if existing port is being … chore: use a new port if existing port is in use Jul 3, 2021
```Note: Please ping us in #contributing channel in our slack community and we will DM you with <test environment URL>```
```Note: Please ping us in #contributing channel in our slack community and we will DM you with <test environment URL>```

### To Avoid Adding a file to git or ignore changes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure, if we need this instructions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jyash97 this is good to know instruct=ions when you want to avoid changs adding to a file

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree this is good to know instructions. But usually project doesnt include git instructions to remove files.

On other note: I have never used this till now 😅

cc @nidhi-tandon @ankitnayan what are your thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not to remove files, for example if you make changes in locale .env files then you dont need to commit them as they are locale
so what you can do ignore them, so any changes you do will not be added to commit

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

README.md should contain info about the projects. Usually, OSS projects have 2 sets of users engaged a) OSS users, and b) OSS developers. The above info seems useful for b) type users. I guess README.md is more focussed on a) type users and CONTRIBUTING.md on b) type users.

Got a nice article on README.md at link. Feel free to emphasize a few points which seem good.

@ankitnayan
Copy link
Collaborator

@rahulrana95 On running yarn install, I see below error:

error An unexpected error occurred: "https://unpm.uberinternal.com/portfinder-sync/-/portfinder-sync-0.0.2.tgz: Request failed \"401 Unauthorized\"".

I did yarn add portfinder-sync and then git diff. I noticed below relevant changes in yarn.lock

-  resolved "https://unpm.uberinternal.com/portfinder-sync/-/portfinder-sync-0.0.2.tgz#6e3409a73a718436de053ac949385350caabd8a2"
+  resolved "https://registry.yarnpkg.com/portfinder-sync/-/portfinder-sync-0.0.2.tgz#6e3409a73a718436de053ac949385350caabd8a2"

Want to change the registry from uberinternal to yarnpkg?

@ankitnayan
Copy link
Collaborator

@rahulrana95 I see conflicting files. Can you update your branch with the latest main and push again?

@ankitnayan ankitnayan merged commit 3acef9c into SigNoz:main Jul 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants