https://github.com/usegalaxy-eu/operations
usegalaxy.eu operations
https://github.com/usegalaxy-eu/operations
documentation operations usegalaxy usegalaxy-eu
Last synced: 5 months ago
JSON representation
usegalaxy.eu operations
- Host: GitHub
- URL: https://github.com/usegalaxy-eu/operations
- Owner: usegalaxy-eu
- License: cc-by-4.0
- Created: 2017-08-28T11:59:43.000Z (almost 9 years ago)
- Default Branch: main
- Last Pushed: 2026-01-16T09:30:29.000Z (5 months ago)
- Last Synced: 2026-01-16T22:46:35.612Z (5 months ago)
- Topics: documentation, operations, usegalaxy, usegalaxy-eu
- Language: Python
- Homepage: https://usegalaxy-eu.github.io/operations/
- Size: 1.67 MB
- Stars: 4
- Watchers: 4
- Forks: 8
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://usegalaxy-eu.github.io/operations/)
# Operations Manual for usegalaxy.eu
- [Custom Subdomain](./subdomains.md)
- [Interactive Tools](./interactive_tools.md)
- [Update a Tool](https://github.com/usegalaxy-eu/usegalaxy-eu-tools)
- [Galaxy Europe Services](./cloud/services.md)
- [Bare metal nodes](./bare_metal.md)
- [Traefik](./traefik.md)
- [Configuring multi-GPU HTCondor nodes](./multi-gpu-single-node-htcondor.md)
Galaxy Admin:
- [Upgrade Procedures](./upgrade.md)
- [Rebasing when upstream gets backports](./rebasing.md)
- [Process Management](./procmgmt.md)
- [TIaaS Requests](./tiaas.md)
- [Jobs](./jobs.md)
- [Monitoring](./monitoring.md)
- [Mixed Notes](./notes.md)
Cloud Admin:
- [VMs overview](./cloud/readme.md)
- [Accessing bwCloud with Terraform](./cloud/access-bwCloud.md)
- [Launching a student VM](./cloud/student-vm.md)
- [Services in the bwCloud](./cloud/services.md)
- [Celery](./celery.md)
This and That:
- [Miscellaneous stuff](./miscellanea/)
## Read-only Fridays
- **NO EXCEPTIONS**
- Do not merge things to the playbook repositories that will be auto-applied
- Do not do any manual systems administration
- Consider writing documentation or more test cases instead.
## Adding a User to Grafana
1. They should [login](https://stats.galaxyproject.eu) using GitHub auth.
- Note that they must be a member of an [approved organisation](https://github.com/usegalaxy-eu/infrastructure-playbook/blob/39d5b7e86b4f45acba53adb965b11b63700327ad/group_vars/grafana.yml#L119). (Note that this link is to a specific revision where I could be sure the line number was correct, please check against `master`)
2. (As an admin) Open [the user list](https://stats.galaxyproject.eu/admin/users/)
3. Find them and "edit"
4. Under "Organizations" type "Main" and select the main organisation that shows up, adding them as the appropriate role.
## (Re-)sending activation links
Some users do not get the activation email or are unable to find it. On request we can generate the link with the
following procedure:
```bash
cd /opt/galaxy/server/
. ../venv/bin/activate
python /data/gxmnt/galaxy-dist/scripts/activation_link.py -c ~/config/galaxy.ini -e
```
## Creating and editing an encrypted file using Ansible Vault
Ansible Vault encrypts variables and files to protect sensitive content such as passwords or keys rather than leaving it visible as plaintext in playbooks or roles.To use Ansible Vault you need one or more passwords to encrypt and decrypt content. If you store your vault passwords in a third-party tool such as a secret manager, you need a script to access them. Use the passwords-with the ‘ansible-vault’ command line tool to create and view encrypted variables, create encrypted files, encrypt existing files, or edit, re-key, or decrypt files.
1. Clone [our repository](https://github.com/usegalaxy-eu/infrastructure-playbook).
2. Navigate to Ansible vault directory `cd infrastructure-playbook/secret_group_vars/`
3. Create a new branch or checkout to the branch you want to switch to, e.g.(‘dp_keycloak’)
4. Use command `ansible-vault create keycloak.yml` to create new encrypt file.
5. Then ansible asks for:
New Vault password:
Confirm New Vault password:
It is recommended to use the previously set Vault password for smooth running of playbook
6. The newly created encrypt file (‘keycloak.yml’) enables us to enter data or enter lines of code before encrypted.
7. The content in the encrypted files can be read by command `ansible-vault view keycloak.yml` and can be edited by the command `ansible-vault edit keycloak.yml` followed by entering the given Vault password.
8. Update the branch pushing commits `git push`