I followed some advice from this discussion, and I created a nixpack file for each of my services (named "web", "worker", & "whenever").

My three nixpack files are named:

• config/railway.web.toml

• config/railway.worker.toml

• config/railway.whenever.toml

Each of these nixpacks includes a [deploy] section with a startCommand.

I've also set the NIXPACKS_CONFIG_FILE environment variable on each of these services accordingly:

• web: NIXPACKS_CONFIG_FILE=config/railway.web.toml

• worker: NIXPACKS_CONFIG_FILE=config/railway.worker.toml

• whenever: NIXPACKS_CONFIG_FILE=config/railway.whenever.toml

Unfortunately, the start command is only being respected by the worker & whenever services; it is not being respected by the web service.

My railway.web.toml file contains the following:

[phases.setup]
providers = ['...', 'ruby']

[deploy]
startCommand = 'bundle exec rails db:prepare db:seed && bundle exec rails server -b 0.0.0.0 -p ${PORT:-3000} -e $RAILS_ENV'

I've made sure to delete both Procfile and Dockerfile that were in my project's root as well.

Is there any other reason that my web service would not be using the startCommand provided in the nixpacks file?