Our server setup script has not been updated yet to account for some changes in our environment:
It still has some manual steps related to deploy keys in GitLab; this needs to be updated to refer to Gitea.
Git has added this brilliant new "safe repository" feature related to manipulating repos from other user accounts (which our deploy scripts use):
# make deploy
/home/hmn/hmn/server/deploy.sh
Type the name of the branch you would like to deploy:
beta
Deploying branch beta...
fatal: unsafe repository ('/home/hmn/hmn' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /home/hmn/hmn
make: *** [Makefile:15: deploy] Error 128
The setup should be changed to account for this, and the entire setup process vetted in DigitalOcean to ensure that it works and we can set up a new instance quickly if necessary.
Our server setup script has not been updated yet to account for some changes in our environment:
- It still has some manual steps related to deploy keys in GitLab; this needs to be updated to refer to Gitea.
- Git has added this brilliant new "safe repository" feature related to manipulating repos from other user accounts (which our deploy scripts use):
```
# make deploy
/home/hmn/hmn/server/deploy.sh
Type the name of the branch you would like to deploy:
beta
Deploying branch beta...
fatal: unsafe repository ('/home/hmn/hmn' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /home/hmn/hmn
make: *** [Makefile:15: deploy] Error 128
```
The setup should be changed to account for this, and the entire setup process vetted in DigitalOcean to ensure that it works and we can set up a new instance quickly if necessary.
Our server setup script has not been updated yet to account for some changes in our environment:
It still has some manual steps related to deploy keys in GitLab; this needs to be updated to refer to Gitea.
Git has added this brilliant new "safe repository" feature related to manipulating repos from other user accounts (which our deploy scripts use):
The setup should be changed to account for this, and the entire setup process vetted in DigitalOcean to ensure that it works and we can set up a new instance quickly if necessary.