From aeae05c91405b1fbd6c06492f1e76ca3a7114f78 Mon Sep 17 00:00:00 2001 From: Tim Turner Date: Fri, 11 Oct 2024 13:40:09 -0700 Subject: [PATCH] README matches INSTALL requirements, grammar fix --- docs/README.md | 13 +++++++++---- docs/admin/SSL.md | 2 +- 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/README.md b/docs/README.md index 2ef596b..43a6326 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,7 +1,7 @@ --- home: true -tagline: Managing an ApisCP platform -actionText: Get Started → +tagline: Managing an ApisCP platform +actionText: Get Started actionLink: /INSTALL/ features: - title: Self-healing @@ -24,8 +24,13 @@ ApisCP is an modern hosting panel + platform that began in 2002 as a panel for A - 2 GB RAM - [Forward-confirmed reverse DNS](https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS), i.e. 64.22.68.1 <-> apnscp.com -- CentOS/RedHat 7+ -- Bare-metal or virtualization (kvm, xen, VMWare, Hyper-V). Containers (OpenVZ, LXC, Docker) are not supported. +- RHEL-based OS: + - RHEL 7.4+ (EOL) / 8.* + - CentOS 7.4+ (EOL) / 8.* + - CentOS Stream 8.* + - Rocky Linux 8.* + - AlmaLinux 8.* +- Containers are **not supported** (Virtuozzo, OpenVZ, LDC, Docker) ## Installation diff --git a/docs/admin/SSL.md b/docs/admin/SSL.md index 2599a51..6abdb0e 100644 --- a/docs/admin/SSL.md +++ b/docs/admin/SSL.md @@ -78,7 +78,7 @@ Domains with managed DNS will consolidate multiple subdomains to a wildcard cert This does not work when the domain's public IP address does not match the expected public IP, such as if the domain is behind [Cloudflare](dns/Cloudclare.md) proxy. ### Staging -Issuance may be staged, that is to say authorization generated using `letsencrypt:challenges()`, then solved at a later time using `letsencrypt:solve()`. Once solved, the a certificate may be ordered for the hostname using `letsencrypt:request()` using the pre-solved challenges as a shibboleth. +Issuance may be staged, that is to say authorization generated using `letsencrypt:challenges()`, then solved at a later time using `letsencrypt:solve()`. Once solved, a certificate may be ordered for the hostname using `letsencrypt:request()` using the pre-solved challenges as a shibboleth. ```bash cpcmd -d site1 letsencrypt:challenges '[*.mydomain.com,mydomain.com]'