#railway up --no-gitignore

43 messages · Page 1 of 1 (latest)

jagged beacon
sonic gyroBOT
#

Project ID: c26b8920-7fe4-424d-a3d7-77ee61a21ac4

jagged beacon
#

c26b8920-7fe4-424d-a3d7-77ee61a21ac4

flint widget
#

that pr may have been merged, but a release containing the flag has not been made yet

jagged beacon
#

So what I should do?

flint widget
#

remove the files from your gitignore

jagged beacon
#

I don't want to rename delete the file each publish...
also in the documentation it says that .gitignore is not used...

flint widget
#

show me the docs that say that? railway up has used the .gitignore file since v0

jagged beacon
#

Can't find it now,
Howeverr the documentation for up don't mention this,
https://docs.railway.app/reference/cli-api#up

And since I am deploying a docker file , I expect that the docker build will happen the same way as on mine machine, So I had build the docker image on mine machine and It had all the files and in your build the files were missing, which is huge misaligment and it not noted anywhere so It took me 2-3 hours to figure out that it's because of .gitignore that you obey for some reason...
.gitignore is for git... you are a difrrent app

Railway Docs

Documentation for Railway

flint widget
#

its true railway is not git, but removing behavior that has been around since v0 of the cli, removing that would break too many things, thats why the flag has been added, docs pending.

jagged beacon
#

ok.
So It will be out in 2-4 weeks ?

flint widget
#

im sorry i dont have a timeline

jagged beacon
#

Ok, I also tried a solution to define
negative rules in your .railwayignore

#

This didin't worked ... or maybe I had missed anything...

flint widget
#

that likely wont work because .railwayignore is loaded before .gitignore for some reason

#

it would always be possible for the cli to be compiled from source

jagged beacon
#

yes... but it's too much , I will implement renaming the file before, and returning it after

#

Thanks for your help 🙂
I really love your platform

flint widget
#

not my platform 🙂 i dont work for railway

jagged beacon
#

Anyhow , you involved 🙂

flint widget
#

but may i ask why you dont let railway create the build artifacts?

jagged beacon
#

You have the train near your name so ... 🙂

flint widget
#

im a conductor (discord mod) the people who work for railway have a railway logo besides their name

jagged beacon
#

railway do 10 step docker build
our file do 4

flint widget
#

do you mean nixpacks?

jagged beacon
#

Yes, It's running some kind of socker build

#

*docker

flint widget
#

yes railway runs on docker

#

what do you mean by "our file"

jagged beacon
#

We run on NodeJS
If it has native runtime without docker we wold deploy .,.

#

Our

#

Dockerfile

flint widget
#

everything on railway is going to be a docker container

jagged beacon
#

Also we have fine control over the nodejs version

flint widget
#

if you have your own Dockerfile railway will use that

jagged beacon
#

Yes , so we have Dockerfile
And it's much faster to build than the nixpacks one

flint widget
#

so why not let railway do the build artifacts?

jagged beacon
#

A... there is some issue ... Which is not happening locally like the local docker file builds normally , creating the artifacts etc...
on railway I get some weird errors...
I didn't dived in ... rename of .gitignore did the trick yesterday , so I didn't dived in....

#

We are a tiny 2 people team, so we prefer to focus on our logic... not dive into some platform stuff yet... 🙂

flint widget
#

fair enough

jagged beacon
#

Thank you very much for your help