Skip to content

After the foreman finishes, the ruby process continues to exist #775

@afuno

Description

@afuno

Ruby 2.7.2, Rails 6.1.0, Foreman 0.87.2


I have two Rails applications. One application depends on another through an API.

I run both applications with two commands in different console windows:

foreman start -f Procfile.dev

Inside these two Procfiles:

web: bundle exec rails s -p 3000
webpacker: ./bin/webpack-dev-server
web: bundle exec rails s -p 3010
webpacker: ./bin/webpack-dev-server
worker: redis-server
worker: bundle exec sidekiq -C config/sidekiq.yml

The application terminates using the keyboard shortcut Control + C.

After that, through the monitoring app on macOS, I continue to see two ruby processes. These processes absolutely appear after the launch of Rails applications. And these processes together load the CPU at 100%.

These two processes have to be completed separately. For some reason, this command is suitable for this:

spring stop

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions