Small-scale-admins

Download

small-scale-admins@lists.galaxyproject.org

June 2025

3 participants
2 discussions

Thursday, June 19th (3PM CEST) - next meeting of the "small scale servers" group
by Hans-Rudolf Hotz 20 Jun '25

20 Jun '25

Dear All Our next meeting will be this week on Thursday (June 19th) at 3PM CEST (1PM UTC) Please add any questions or topics you would like to discuss to our rolling minutes document: https://docs.google.com/document/d/1KTz4qxZBG4Z3sF23dVKPWXYz1mCNo2YDygSUHqt… Zoom link: https://unige.zoom.us/j/67916443799?pwd=ade4kVZgKinYAafDZnGKwomJM0ub0Q.1 Regards, Lucille and Hans-Rudolf PS: next meetings for your calendar: July 17th, 3PM CEST (1PM UTC) August 21st, 3PM CEST (1PM UTC) September 18th, 3PM CEST (1PM UTC) October 16th, 3PM CEST (1PM UTC)

2 1

deploying Galaxy for the first time
by Juan Antonio Cordero Varela 17 Jun '25

17 Jun '25

Dear small scale Galaxy Admins, I am planning to deploy a production Galaxy Server to be used by the researchers at my research institute. I have been following the tutorials at Galaxy Training! <https://training.galaxyproject.org/training-material/learning-pathways/admi…> and some questions have come to mind: * *OS version*: Ubuntu 22.04 vs 24.04?: since the tutorial is a bit old already (based on Ubuntu 18.04), I assume I should stick to the latest stable Ubuntu version. * Should I install the *latest stable Galaxy* version (25.0 at this moment)? * Should Galaxy server be *on a VM or on a physical node*? My HPC infrastructure consists of login and management nodes working as VMs inside a Proxmox 7.X server, and a bunch of computing nodes (there's a couple dedicated storage nodes). If Galaxy and the PostgreSQL database are stored on the same VM and it has enough resources it would be quite easy to manage, since you can reboot it very quickly and it's possible and easy to take snapshots of the VM. * If the Galaxy Server is stored on a VM on the Proxmox host, I would not be able to access the VM directly from outside. Which changes should I make to access the Galaxy? Is there any alternative to redirect traffic to port 80 or 8080 from the Proxmox host to the VM? I’ve experienced some issues with Nginx if I do this, since Gunicorn uses a gunicorn.sock file instead. If I add iptables rules so that the proxmox server redirects all the traffic from its port 80 to the port 80 of the VM, I get the following error at nginx: |nginx: 2025/06/13 10:55:55 [crit] 46578#46578: *1 connect() to unix:/srv/galaxy/var/config/gunicorn.sock failed (2: No such file or directory) while connecting to upstream, client: 10.X.X.X, server: 192.168.2.X, request: "GET / HTTP/1.1", upstream: "http://unix:/srv/galaxy/var/config/gunicorn.sock:/", host: "10.X.X.X", referrer: "http://10.X.X.X/"| I've read I should use NGINX on the Proxmox host if I don't want to do port-forwarding with iptables. Alternatively the VPN from the research institute could be reconfigured or redirect directly to the VM. Do you have any thoughts about this? If this is not the right channel to ask, please let me know. Thanks a lot in advance, Cheers, Juan

2 1