2 months ago
Hello ! I'm trying to deploy a rust app. I gave specific deployment and run commands. Deployment is fine, but it never finds the exe, so I ended up replacing my custom run command by ls -a and saw there wasn't a target folder (which is where builds are outputed usually).
custom build command: cargo +nightly build --release
custom start command: ./target/release/steel (steel being the name of the project)
In case you need more context, the repo i'm trying to deploy is: https://github.com/4lve/SteelMC
I tried to use cargo to run the project, but it seems cargo isn't available during runtime phase. I also provided my logs. The fact that I have to build from the nightly channel might not help :/
Ty for reading
41 Replies
2 months ago
Hey, I did some tests and that looks like to be a bug with Railpack (our build system at ), I'll confirm in more details but I'll recommend using a Dockerfile with that project for now
2 months ago
If you're not familiar with Dockerfile, we can create one together 🙂
hello, yes, I used a dockerfile instead, the server runs, but crashes as soon as i try to connect to it (it's a minecraft server) i use the TCP proxy as minecraft packets uses TCP connection. The same docker image works flawlessly locally, but on railway it crashes as soon as it receives the connection
2 months ago
What kind of crash error are you getting?
2 months ago
Oof, do you by any chance have that repository with a Dockerfile publicly available?
2 months ago
Will take a look, give me a sec
thanks a lot for your help, but i have nothing to give you in return, it's not that urgent, it's the weekend
2 months ago
Weirdly enough I was able to connect without any problems

2 months ago
Don't worry about it, I just like doing this
2 months ago
In case you want to test it out
2 months ago
centerbeam.proxy.rlwy.net:48424
2 months ago
Seems like it only supports 1.21.11
2 months ago
Just Vanilla
2 months ago
I didn't change anything, I just assigned a TCP proxy to it pointing to Minecraft's 25565 port

2 months ago
it seems to use a lot of CPU in the start

2 months ago
Try removing/increasing the resource limitation and see how it goes
there must be something i'm doing wrong. I created a new one from scratch, added tcp, it started, but crashes once i connect
2 months ago
That's weird, are you on the Hobby plan?
2 months ago
I'll try but I didn't really change anything
just to see if it's me, or maybe the project the service is on… I didn't change anything too
also, i knew your name reminded me of something, i'm actually using your nestjs better auth adapter, it's great, thanks a lot
2 months ago
here, see if you can deploy it
https://railway.com/deploy/ZqFTYE
also, I tried limiting the resources to the same as the hobby plan (8gb and 8vcpu) and I still was able to connect to it without any problems, even when limiting it down to 4gb and 4vcpu
yamabiko.proxy.rlwy.net:52178
can you try to connect to mine? After all, it might be my minecraft
2 months ago
Yeah I get disconnected and then the server crashes probably
i mean on local it works on 1core 512mb of ram, so resources aren't the reason why this is crashing
Status changed to Solved passos • 3 months ago