[x]
):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
.
It can be changed and I don't think anyone would run Gogs and Gitea on same server
i run both in same server! also for packgin purposes its necesary and to take care of standars!
Changing default port would break existing installations and for such rare cases as yours you can change port to other in your config file
but this way its no standar, i not see that newer software try to overlaping ports of another in "same" category
Run nginx and apache this "same" server...
That's why you set your preferences in the configuration file.
Run both Gogs and Gitea on same machine is strange.
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
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
.
Most helpful comment
Run nginx and apache this "same" server...
That's why you set your preferences in the configuration file.