The main Perdigao data system configuration is in the public-field-projects repository on github.com: https://github.com/ncareol/public-field-projects. Despite the name, this repository is no longer public, so your github account must have been given permission to access this repository.
This configuration is deployed to many places. It is used to run the data processing on ustar and at EOL on barolo, besides existing on every single DSM in perdigao. So it is important use revision control to keep the configuration consistent and to track all the changes.
This presents some challenges using git on the shared daq and isfs accounts. The basic tips are available on this software engineering wiki page:
The quick reference section provides enough to get started, but there are lots of details there in case of questions. After logging in with the sshgit script posted on that page, you should be able to commit in <home>/isfs/projects, and you will be recorded as the git author. Of course, this assumes that you are set as the git author on the host from which you're logging in. In summary:
Make sure git config user.name and git config user.email are correct, otherwise set them like so:
git config --global user.name "First Last" git config --global user.email "firstname.lastname@example.org"
Make sure your current session can authenticate to github:
git ls-remote email@example.com:/ncareol/public-field-projects
If not, follow the steps on github.com to create a SSH key and authorize it for your github.com account.
Log into the remote shared account with the script:
Use git as usual on the shared account:
The same steps work for logging into the isfs account on barolo. However, for that account, the operational configuration under ~isfs/isfs has group write permissions, so EOL users should be able to pull into that repository while logged into their own account. You can also edit, commit, and push, but we risk interfering if multiple people edit there. Same goes for /net/isf/isfs/projects.
Initial project creation:
If you forget to use the sshgit script to log in, you may still be able to commit to a repository, but the author of the commit will be wrong. You can fix it like so:
First log off the remote host. Log back in with sshgit. cd to the repository Fix the last commit: git commit --amend --reset-author
The git command will also prompt for a new commit message, but the previous commit message is provided as a default.