-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improve deployment documentation #144
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for open-terms-archive-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -312,7 +312,7 @@ On your local machine: | |||
|
|||
#### Create the SSH key | |||
|
|||
- Create a new SSH key: `ssh-keygen -t ed25519 -C [email protected] -P "" -f ./<collection_name>-key` | |||
- Create a new SSH key: `ssh-keygen -t ed25519 -C [email protected] -P "" -f ~/.ssh/<collection_name>-key` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why creating this key in your ssh folder whereas it should be deleted from your computer after backing it up and attached to the OTA-Bot user?
@@ -193,7 +193,7 @@ Before proceeding with deployment, ensure that the server meets the following re | |||
- Add the following line at the end of this section: | |||
|
|||
```shell | |||
<user> ALL=(ALL) NOPASSWD:ALL | |||
<username> ALL=(ALL:ALL) NOPASSWD:ALL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need to allow the user to specify both the target user and group when using sudo
?
Makes minor improvements to deployment documentation.