Update the server setup script for Gitea / "safe" features #14

Open
opened 2022-05-21 22:42:14 +00:00 by bvisness · 0 comments
Owner

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.
bvisness added the
admins only
label 2022-05-21 22:43:11 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hmn/hmn#14
No description provided.