Feature Request- possibility to run app on any port

[Voicu-Paul61]

Describe the feature

So I plan on self-hosting this on a machine that has many other self-hosted services and that means that port 3000 might be used so I want to be able to change the port and switch to whatever port I want, changing it in the compose file doesn't do anything as when I go to ip:port I get ip:port didn't send any data and the logs still show that it is starting on 3000 even if it doesn't start it on 3000

Why is this feature important?

Openness to different environments

Additional context, screenshots, and relevant links

No response

[kiguigui]

It seems that this is already possible. In the .env.example-File there is an ENV called PORT= with the following description:

# For users who have other applications listening at 3000, this allows them to set a value puma will listen to.``` 

[darkkon21218]

I am also having a similar issue, I specify my new port in the .env file with PORT=3001, but Puma still starts on 3000.

[darkkon21218]

I found a solution

Specify in the compose.yml file

environment:
PORT: 3001

[zachgoll]

I'm going to close this since this is fully supported.

To run the Rails app on a different port, specify it in your .env file:

PORT=4000

To run the Docker Compose stack on a different port, you'll need to map from your Rails port to the appropriate system port:

ports:
  # app will be available on port 4000, while the Rails app runs on port 3000
  - 4000:3000