Skip to content

Corrected setup naming #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Corrected setup naming #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ By supporting multiple systems, it simplifies certificate management for develop
* Maintain strong HTTPS security standards
* Save time with reliable automation
* Standardize renewal workflows across different platforms
* Centralized management certificates and logging
* Centralized management for certificates and logging
* No SPOF due to wildcard certificates (each instance get's a unique domain specific certificate)
* Easily scalable

Expand Down Expand Up @@ -95,12 +95,12 @@ Follow these steps to get the tool up and running:

> ⚠️ **Important:** Certicopter does not provide built-in interfaces for resolving or securing credentials. All sensitive information - such as passwords, usernames, domain names, API tokens, and similar - is expected to be supplied via environment variables. The mechanism responsible for storing and providing these environment variables must be maintained by the user.

> As part of the guided setup, users receive a template tailored to their requirements. This template includes a checklist of the necessary environment variables but does not handle their the provisioning or secure storage.
> As part of the setup, users receive a template tailored to their requirements. This template includes a checklist of the necessary environment variables but does not handle the provisioning or secure storage.

3. **Network Requirements**
- HTTPS/HTTP access to target systems
- DNS resolution for target domains
- Port access (varies by system and you configurations, typically 80, 443, 8443, 9440, 9443)
- Port access (varies by system and your configurations, typically 80, 443, 8443, 9440, 9443)

### Setup

Expand Down Expand Up @@ -184,7 +184,7 @@ To ensure your SSL certificates are automatically renewed before they expire, yo

### Configuration

The application uses a JSON-based configuration file (`config.json`) with the following example structure (generated automatically with the guided setup process):
The application uses a JSON-based configuration file (`config.json`) with the following example structure (generated automatically with the setup process):

```json
{
Expand Down