Skip to content

Clarify environment variables to be base64 encoded #296

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

Merged
poespas merged 1 commit into from
Dec 20, 2024
Merged

Clarify environment variables to be base64 encoded #296

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
4 changes: 2 additions & 2 deletions docs/hypernode-deploy/getting-started/configure-ci-cd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ In this example we'll be covering the Github Actions CI/CD configuration.

Hypernode Deploy needs a few 'credentials' to be able to function. The necessary credentials are:

1. The private SSH key. (`SSH_PRIVATE_KEY`)
1. The composer auth.json file, optional. (`DEPLOY_COMPOSER_AUTH`)
1. The private SSH key as base64 encoded string. (`SSH_PRIVATE_KEY`)
Copy link
Member

@tdgroot tdgroot Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is optional actually, but can't hurt

1. The composer auth.json file as base64 encoded string, optional. (`DEPLOY_COMPOSER_AUTH`)
- This is only necessary when your project needs to access private Composer repositories.
1. The Hypernode API token, optional. (`HYPERNODE_API_TOKEN`)
- This is only necessary when you make use of Hypernode API driven features like Brancher.
Expand Down
Loading