Project

General

Profile

Actions
Copy link

Bug #33956

closed

serve assets directly via Apache, not via Puma/Rails

Added by Evgeni Golov about 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Evgeni Golov
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-foreman/pull/1078, https://github.com/theforeman/puppet-katello_devel/pull/285, https://github.com/theforeman/puppet-foreman/pull/1085, https://github.com/theforeman/puppet-foreman/pull/1101
Fixed in Releases:
Foreman - 3.5.0
Found in Releases:
Foreman - 3.1.0
Red Hat JIRA:

Description

Right now, we don't special-case our assets folders in Apache, which results in these requests hitting Rails instead of being served directly by Apache (which should be 1000000× faster).

Ewoud said this is because it was tried to be implemented when we switched from Passenger to Puma, but Katello assets were broken afterwards, details in https://projects.theforeman.org/issues/35409

Subtasks 3 (0 open — 3 closed)

SELinux - Bug #35402: Allow apache to read /var/lib/foreman/publicClosedEvgeni GolovActions
Foreman - Bug #35403: Disable public_file_server in productionClosedEvgeni GolovActions
Packaging - Bug #35409: make sprockets-based plugin assets reachable from within /var/lib/foreman/public/assetsClosedEvgeni GolovActions

Related issues 2 (0 open — 2 closed)

Related to Packaging - Bug #35997: Legacy rex form is missing options for future or recurring executionClosedEvgeni GolovActions
Related to Katello - Bug #37133: /katello/sync_management tries to use /assets/spinner.gif but that's 404ClosedJeremy LenzActions
Actions
Copy link

Also available in: Atom PDF