nwtgck / piping-server

Infinitely transfer between every device over pure HTTP with pipes or browsers
MIT License
2.92k stars 153 forks source link

Request: support defining the options in a .env file #927

Closed Sov3rain closed 4 months ago

Sov3rain commented 4 months ago

Hey there!

First of all, thank you for this great project. I want to deploy my own instance on Railway.app (similar to Heroku). I choose the option to deploy from a GitHub repo directly. It apparently uses the Dockerfile in the project and deploys the thing. It all starts to fall apart when Railway tries to launch the server: the port should not be defined manually but instead Railway should inject it when starting the server.

Right now I see no ability to get this port variable outside of the args from the start command. Is there any chance that it exists and I didn't notice?

Sov3rain commented 4 months ago

Nevermind, I found a solution. For those ending here, follow the following steps to be able to deploy to Railway.app: