Project

General

Profile

Actions

Tracker #28999

closed

Deploy Foreman with Puma as the application server by default

Added by Eric Helms almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
% Done:

0%

Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Related issues 11 (2 open9 closed)

Related to Packaging - Bug #17712: Passenger can't find passenger_native_support.soRejectedActions
Related to Foreman - Feature #28955: Add Puma workers/threads configurationClosedSuresh ThirugnanasambandanActions
Related to Installer - Bug #29041: Update Puma default workers from 5 to 2 in the devel scenarioClosedSuresh ThirugnanasambandanActions
Related to Foreman - Feature #29148: Make puma defaultClosedSuresh ThirugnanasambandanActions
Related to Installer - Feature #29282: Add migrations for replacing passenger with pumaClosedSuresh ThirugnanasambandanActions
Related to Foreman - Bug #29507: Add puma-status to report puma statusingClosedEric HelmsActions
Related to Packaging - Feature #29514: package puma-status gemClosedEric HelmsActions
Related to Katello - Bug #29370: Syncing a large product leaves Pulp tasks "waiting".NewActions
Related to Foreman - Bug #29588: Foreman service seems active however keeps restarting if it can't startNewActions
Related to Foreman - Feature #29356: Ship Puma systemd plugin in productionClosedEwoud Kohl van WijngaardenActions
Related to Foreman - Feature #29584: Preload application with Puma in production modeClosedEwoud Kohl van WijngaardenActions
Actions

Also available in: Atom PDF