Configure nixpacks.toml per service | Railway | Page 1

leaden falcon Dec 10, 2022, 11:45 PM

#

Is it possible to have multiple nixpacks.toml file on repo and config which each service should use?

I'm currently having 3 services on every project:

If I could choose different builds for each I could have slightly different builds. (like not compiling assets)

young harborBOT Dec 10, 2022, 11:45 PM

#

Project ID: 2bda3e88-4f1a-4742-80c7-24f5e032f52c

#

Yes, it is possible to have multiple nixpacks.toml files in a repo and configure which service should use which file.

leaden falcon Dec 10, 2022, 11:46 PM

#

project id: 2bda3e88-4f1a-4742-80c7-24f5e032f52c

leaden falcon Dec 12, 2022, 1:02 PM

#

how?

young harborBOT Dec 12, 2022, 1:02 PM

#

Yes, it is possible to have multiple nixpacks.toml files for different services, and you can configure builds with a nixpacks.toml file.

distant scroll Dec 12, 2022, 3:22 PM

#

lmao

#

I’m assuming you’re using a monorepo, how is it structured?

#

if you set a separate root directory for each service, each root directory can have a nixpacks.toml

leaden falcon Dec 12, 2022, 3:25 PM

#

It's a RubyOnRails app. Monorepo, yes. but only one root directory.
On other platforms I'd have different processes configured on Procfile.

#

The 3 services I'm running are actually the exact same app. Only difference is the process that runs.

#

Currently it works fine configuring the start command through railway.app UI
but i could optimize deploys by setting nixpacks file per service.

cyan walrus Dec 12, 2022, 4:47 PM

#

You can configure separate nixpacks.toml using railway.toml

#

and railway.toml can be configure in settings (This feature is in beta. Please use </beta:933628896727945218>)

#

#Configure nixpacks.toml per service