@ekohl can you help me formulate a prerequisite for chapter two for Foreman EL and Katello users.

To use this section, you must have foreman-maintain installed (how do they do that?)
And is there an alternative method? I can add that in?
At the moment, i've just added an ifndef for foreman-deb builds for Chapter 2.

To use this section, you must have foreman-maintain installed (how do they do that?)

For Foreman on EL, you can yum/dnf install it. For Debian you can't. The software doesn't support it and is also not packaged.

Personally I always use systemctl directly.

systemctl stop foreman.service foreman.socket to stop Foreman itself. For something like (re)start it's sufficient to only restart foreman.service. There's also dynflow-sidekiq@* (always recommend to use \* if it's a shell command to prevent globbing files).

You should also be aware that httpd (EL) or apache2 (Debian) is a service that's used on the Foreman server. There's also rh-redis5-redis (EL7) or redis (EL8 / Debian).

If you're using a DB on the same server, there's also postgresql.service.

If I want to manage the Foreman Proxy, it's systemctl $action foreman-proxy.service. $action can be status, stop, start and restart.

orcharhino is currently using a version of "Administering Foreman" somewhere between foreman-el and satellite. For us, Katello is a non-optional plugin and orcharhino only runs on EL (7) currently.

Please tag me @melcorr whenever there are changes regarding the versions for foreman-el, satellite, and orcharhino.

There's also dynflow-sidekiq@* (always recommend to use \* if it's a shell command to prevent globbing files).

I don't understand this bit. At the moment, I have created a prerequisite section where I say that before they can use the procedure, they'd have to have foreman-maintain installed, then the command. Then I say, Alternatively, they can use systemctl and the range of options for starting and stopping.

I'm assuming dynflow-sidekiq@* is a service they need to consider? Starting and stopping it? Starting it as part of the restart?

I've revisited this a bit and opened #979 which is certainly not a solution, but a step in the right direction.

We now provide Administering Foreman for both EL and Debian:

• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-el.html
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html

To me, that suggests that the goal set in this issue's description has been met. Am I missing anything? Or can we close this issue?

@asteflova To me, this is done after we remove HideDocumentOnStable for this guide.

• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#Estimating_the_Size_of_a_Backup_admin mentions Pulp
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#Performing_a_Backup_Without_Pulp_Content_admin should be hidden for foreman-deb and foreman-el
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#Performing_an_Online_Backup_admin mentions Pulp
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#Synchronizing_Content_from_foreman_Server_to_Smart_Proxy_Servers_admin should be hidden for foreman-el and foreman-deb
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#Using_the_Project_Content_Dashboard_admin mentions errata with should be hidden AFAIK for foreman-el and foreman-deb (unsure if you can view errata from your OS vendor on foreman-el/-deb?)
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#viewing-general-smart-proxy-information_admin mentions Pulp which is wrong for foreman-el and foreman-deb
• https://docs.theforeman.org/nightly/Administering_Project/index-foreman-deb.html#webhooks-available-events_admin mentions a lot of Katello-related hooks.

summary: IMHO still requires some work but we're close to showing the Administering Foreman guide to Foreman on EL/Foreman on Deb soon.