bug: default port conflict with existing software #1062

Closed
opened 2025-11-02 03:46:54 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @mckaygerhard on GitHub (Sep 14, 2017).

  • Gitea version (or commit ref): any
  • Git version: 1.8.4
  • Operating system: Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Gitea was after gogs, so the default port must be changed, gogs already setup already times ago in port 3000,

so it's time gitea have their own port. not only a rename of any "gogs" word in the sources
.

Originally created by @mckaygerhard on GitHub (Sep 14, 2017). - Gitea version (or commit ref): any - Git version: 1.8.4 - Operating system: Linux - Database (use `[x]`): - [x] PostgreSQL - [x] MySQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Gitea was after gogs, so the default port must be changed, gogs already setup already times ago in port 3000, so it's time gitea have their own port. not only a rename of any "gogs" word in the sources .
Author
Owner

@lafriks commented on GitHub (Sep 14, 2017):

It can be changed and I don't think anyone would run Gogs and Gitea on same server

@lafriks commented on GitHub (Sep 14, 2017): It can be changed and I don't think anyone would run Gogs and Gitea on same server
Author
Owner

@mckaygerhard commented on GitHub (Sep 14, 2017):

i run both in same server! also for packgin purposes its necesary and to take care of standars!

@mckaygerhard commented on GitHub (Sep 14, 2017): i run both in same server! also for packgin purposes its necesary and to take care of standars!
Author
Owner

@lafriks commented on GitHub (Sep 14, 2017):

Changing default port would break existing installations and for such rare cases as yours you can change port to other in your config file

@lafriks commented on GitHub (Sep 14, 2017): Changing default port would break existing installations and for such rare cases as yours you can change port to other in your config file
Author
Owner

@mckaygerhard commented on GitHub (Sep 14, 2017):

but this way its no standar, i not see that newer software try to overlaping ports of another in "same" category

@mckaygerhard commented on GitHub (Sep 14, 2017): but this way its no standar, i not see that newer software try to overlaping ports of another in "same" category
Author
Owner

@lcges commented on GitHub (Sep 20, 2017):

Run nginx and apache this "same" server...
That's why you set your preferences in the configuration file.

@lcges commented on GitHub (Sep 20, 2017): Run nginx and apache this "same" server... That's why you set your preferences in the configuration file.
Author
Owner

@lunny commented on GitHub (Sep 20, 2017):

Run both Gogs and Gitea on same machine is strange.

@lunny commented on GitHub (Sep 20, 2017): Run both Gogs and Gitea on same machine is strange.
Author
Owner

@bkcsoft commented on GitHub (Oct 21, 2017):

Gogs (and subsequently Gitea) just uses the same port that most other services use (gitlab, node-express, python-flask, etc) so this is a non-issue, change the port for one of the services either by editing the config or by running ./gitea web --port 3001

@bkcsoft commented on GitHub (Oct 21, 2017): Gogs (and subsequently Gitea) just uses the same port that most other services use (gitlab, node-express, python-flask, etc) so this is a non-issue, change the port for one of the services either by editing the config or by running `./gitea web --port 3001`
Author
Owner

@mckaygerhard commented on GitHub (Oct 22, 2017):

now i know why distributions package fisrt the gogs event gitea

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

2017-10-21 12:55 GMT-04:00 bkcsoft notifications@github.com:

Gogs (and subsequently Gitea) just uses the same port that most other
services use (gitlab, node-express, python-flask, etc) so this is a
non-issue, change the port for one of the services either by editing the
config or by running ./gitea web --port 3001


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/2509#issuecomment-338416496,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABf7jE5OmguQoiq2UgRIQns3urJZUkqcks5suiIKgaJpZM4PX8n6
.

@mckaygerhard commented on GitHub (Oct 22, 2017): now i know why distributions package fisrt the gogs event gitea Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-10-21 12:55 GMT-04:00 bkcsoft <notifications@github.com>: > Gogs (and subsequently Gitea) just uses the same port that most other > services use (gitlab, node-express, python-flask, etc) so this is a > non-issue, change the port for one of the services either by editing the > config or by running ./gitea web --port 3001 > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/go-gitea/gitea/issues/2509#issuecomment-338416496>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABf7jE5OmguQoiq2UgRIQns3urJZUkqcks5suiIKgaJpZM4PX8n6> > . >
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1062