Ruby: Rails build fails when configured as an api

[taphill]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I ran into a build failure when attempting to deploy a new Rails API to Railway using the railway up command.

It appears that the build fails when it tries to run this rake task assets:precompile

This is because when you create a rails project with the --api flag it skips all the views, assets, etc. as outlined in the Rails docs here, so the assets:precompile task does not exist.

I think this is the function that probably needs to be updated

It looks like you're looking within the config/application.rb file. Perhaps you can add some logic to look for the config.api_only = true line and adjust the build settings based on that.

To reproduce

1. In the Railway dashboard, create a new empty project
2. On your local machine, create a new rails API with a postgres db rails new my_api --api --database=postgresql
3. Create and migrate the db rails db:{create,migrate}
4. Back in the Railway dashboard click the button at the bottom to set up your project locally
5. Copy the Railway link to connect to the Railway project and paste it into your terminal
6. Run railway up

Expected behavior

I would expect the build to succeed.

Environment

MacOS 12.3.1
ruby 3.2.0
rails 7.0.4

[taphill]

I've not ever used Rust before and don't know how complicated this would be to fix, but I'd be happy to try and submit a PR if this is a rails feature you want to support.

[fusion2004]

I think you can fix this in a nixpacks.toml config file:

[phases.build]
cmds = [] # remove this to re-enable asset building