Remove leftover Cloud66 custom_web process from Procfile

Open Beginner friendly
  • Is something wrong?
#7,330 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ShahadatTest is already working on this.

Since Nov 2, 2026.

  • #7331 by @ShahadatTest — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, rails, ruby, shell
Domain
devops

Research direction

The stray process is the custom_web: bundle exec puma line in the root Procfile; delete it and leave release and web alone. Then run grep -rni "custom_web\|cloud66" . excluding node_modules and check app.json for the same name. Done when the grep finds no leftover references and the PR body says "Closes #7330"; no tests apply and Procfile.dev stays untouched.

Written by the indexing model from the issue text.

Description

Difficulty: Easy Good First Issue

What

The production Procfile still has a custom_web process left over from when the app was deployed on Cloud66:

release: bundle exec rake db:migrate && bundle exec rake after_party:run
web: bundle exec puma
custom_web: bundle exec puma   # <- remove

It came from commit 05d5801e7 ("tell cloud66 to use puma like we currently do"). The app runs on Heroku now, and nothing uses custom_web. Heroku lists it as a dyno type that is scaled to 0. It's harmless but confusing: it looks like a second web process.

The Heroku dashboard also shows a worker: bundle exec rake jobs:work dyno type scaled to 0. It isn't in the Procfile (Heroku is remembering it from an old Procfile). Background jobs currently run through a Heroku Scheduler entry (rake jobs:workoff every 10 min), not a worker dyno.

Task (contributor)

  • Delete the custom_web: bundle exec puma line from Procfile
  • grep -rni "custom_web\|cloud66" . (excluding node_modules) and remove any other leftover Cloud66 references, if there are any
  • Check that app.json doesn't reference custom_web
  • Open a PR that says "Closes #"

There are no Ruby code changes and nothing to test locally. bin/dev uses Procfile.dev, which this doesn't touch.

Follow-up (maintainer, after merge and deploy)

Once a deploy runs without custom_web in the Procfile, Heroku should drop it from the formation. If it or worker is still listed, check with:

heroku ps:type -a casa-production

Both are scaled to 0, so they cost nothing; this is cleanup only.

Out of scope

Don't add a worker: line. Turning on a worker dyno is a separate cost/ops decision; the job queue runs through Scheduler for now (see #7291).

Dominant language
Ruby
Stars
382
Forks
547
Avg merge
2d 22h
Merged PRs (30d)
46

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rubyforgood/casa

All issues in rubyforgood/casa

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.