Skip to content
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.

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

readme: add instructions for non-nix-shell #22

Closed
wants to merge 1 commit into from

Conversation

amyipdev
Copy link
Contributor

@amyipdev amyipdev commented Mar 9, 2024

This patch adds additional information to the README on necessary instructions for using the acm-aws repository without nix-shell.

Environment variables stored in the .env are necessary for performing many acm-aws functions, including usage of the SSH script. Sourcing the .env is necessary to be able to use the SSH script.

When logging in with nix-shell, the .env is automatically sourced, preventing users from having any issues. However, there are currently no indicators that the file needs to be sourced - .env is not even mentioned at all in the README. We don't currently specify in the README that nix-shell is a requirement - in fact, it is listed as optional/highly recommended - and thus non-nix-shell logins should be supported.

Assuming basic dependencies (jq) are installed (doesn't even need Terraform or AWSCLI2), sourcing the .env (with allexport, as the file does not currently actually export the environment variables) and ./secrets is decrypted (with proper permission overrides on the SSH key) is a sufficient condition for being able to log in with SSH.

Signed-off-by: Amy Parker [email protected]

This patch adds additional information to the README on necessary instructions for using the `acm-aws` repository without `nix-shell`.

Environment variables stored in the `.env` are necessary for performing many `acm-aws` functions, including usage of the SSH script. Sourcing the `.env` is necessary to be able to use the SSH script.

When logging in with `nix-shell`, the `.env` is automatically sourced, preventing users from having any issues. However, there are currently no indicators that the file needs to be sourced - `.env` is not even mentioned at all in the README. We don't currently specify in the README that `nix-shell` is a requirement - in fact, it is listed as optional/highly recommended - and thus non-nix-shell logins should be supported.

Assuming basic dependencies (jq) are installed (doesn't even need Terraform or AWSCLI2), sourcing the `.env` (with `allexport`, as the file does not currently actually export the environment variables) and `./secrets` is decrypted (with proper permission overrides on the SSH key) is a sufficient condition for being able to log in with SSH.

Signed-off-by: Amy Parker <[email protected]>
@diamondburned
Copy link
Member

diamondburned commented Mar 9, 2024

.env will be dropped once #21 is merged. I don't think it's feasible to support this use case, as it makes working with the repository a lot more annoying. Any server interaction done locally and not through the GitHub Actions should be assumed to require Nix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants