Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

collectiveidea / delayed_job Public

forked from tobi/delayed_job

Notifications You must be signed in to change notification settings
Fork 954
Star 4.8k

Code
Issues 71
Pull requests 67
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Add an --ontop arg to keep the process alive for heroku#725

Closed

joshco wants to merge 4 commits intocollectiveidea:mastercollectiveidea/delayed_job:masterfrom joshco:masterjoshco/delayed_job:masterCopy head branch name to clipboard

+11-2

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Oct 8, 2014

add ontop = true in daemonize init
joshco
committed
add --ontop option to keep the parent alive. Don't exit after spawning. This will allow heroku dynos to work
joshco
committed
updated readme
joshco
committed
updated readme
joshco
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.