Add Procfile for deploying the dummy app to Heroku#282
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The dummy Rails app has no Gemfile of its own; it depends on the root Gemfile (gemspec) and the gem's lib. A subtree push of test/dummy has no Gemfile at its root, so Heroku's Ruby buildpack never ran and it fell back to Node. Deploy the whole repo with a root Procfile that runs the app from test/dummy instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
FilisLiu
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Adds a
Procfileso the dummy app can run on Heroku, booting it under Puma.Why?
Gives us a live, deployed instance of the dummy app for demoing and reviewing shipped components without each reviewer running it locally.
How?
Procfileweb:process:cd test/dummy, ensuretmp/pidsexists, precompile assets, prepare + seed the DB, then boot Puma. Deploys are justgit push heroku main.Testing?
Manual: deployed to the Heroku app and confirmed the dummy app boots and serves.
Anything Else?
No shipped-component or gem changes — deploy config only.