content: creating a deploy user
This commit is contained in:
parent
af0af59c28
commit
f24f9f1fc7
1 changed files with 19 additions and 0 deletions
|
|
@ -57,3 +57,22 @@ deployment functions on the server from any client.
|
||||||
|
|
||||||
Next need to add deploy user's key to Forgejo eolas-api repo and test the action
|
Next need to add deploy user's key to Forgejo eolas-api repo and test the action
|
||||||
again
|
again
|
||||||
|
|
||||||
|
## Rewrite later:
|
||||||
|
|
||||||
|
This:
|
||||||
|
|
||||||
|
```
|
||||||
|
sudo chown -R deploy:deploy /data/sqlite/eolas
|
||||||
|
sudo chmod -R 770 /data/sqlite/eolas
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Doesn't require the user to be specified in the chmod because the preceding
|
||||||
|
chown makes him the owner.
|
||||||
|
|
||||||
|
This invites a problem though - what if you need multiple owners each with
|
||||||
|
certain permissions. This is when you would use a group.
|
||||||
|
|
||||||
|
In this scenario, the data will only need to be accessed by `deploy` so it is
|
||||||
|
sufficient to make him the sole owner.
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue