-
Notifications
You must be signed in to change notification settings - Fork 6
Improve deployment documentation #144
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -183,8 +183,8 @@ Before proceeding with deployment, ensure that the server meets the following re | |
|
||
- Make sure that a non-root user has been set up on the server, if not you can create by following: | ||
|
||
- Once logged in on your server, create a new user: `adduser <user>`. Follow the prompts to set a password for the new user and provide any additional information if required. | ||
- Grant sudo privileges: `usermod -aG sudo <user>`. | ||
- Once logged in on your server, create a new user: `adduser <username>`. Follow the prompts to set a password for the new user and provide any additional information if required. | ||
- Grant sudo privileges: `usermod -aG sudo <username>`. | ||
|
||
- Grant `sudo` rights to the designated user without requiring a password prompt. To achieve this: | ||
|
||
|
@@ -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 | ||
``` | ||
|
||
### Define the inventory | ||
|
@@ -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 commentThe 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? |
||
- Copy the generated private key file | ||
|
||
#### Encrypt private key and update deployment | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
?