![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 4 years ago
Last modified 4 years ago
#6384 assigned enhancement
Host Trac using a cloud service
| Reported by: | Tom Goddard | Owned by: | Zach Pearson |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Infrastructure | Version: | |
| Keywords: | Cc: | chimerax-programmers, Scooter Morris | |
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
We should investigate hosting our Trac databases for Chimera and ChimeraX using a commercial cloud service. The advantages would be that the provider maintains Trac and updates it and assures it is reliable. Currently our UCSF hosted Trac database often gets corrupted which reduces our productivity.
Change History (3)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Not entirely sure AWS images place _all_ maintenance on us. Upgrades, yes.
https://docs.bitnami.com/general/apps/trac/administration/upgrade/
but the procedure seems short (perhaps deceptively so?)
I anticipate email being the big kicker.
https://docs.bitnami.com/general/apps/trac/configuration/configure-smtp/
comment:3 by , 4 years ago
Tangentially, the current Trac maintainer claims that a 1.6 release may be far off ("no promises") and that the developer build of Trac 1.5 is "very stable".
Zach says our Trac database is ~330 Mbytes (I guess ChimeraX only?) and Lnode offers $10/mo hosting for 1 cpu, 2 gb memory, 50 gb storage, 2 TB transfer (per month?). Or VMware offers Trac AWS image through BitNami at about the same cost. Says Linode is just a cloud machine and we would have to maintain Trac. So that doesn't seem too helpful. Likewise AWS images put the burden of Trac maintenance on us.
Tom notes we need email2trac to work. Zach says the only plugin our Trac has enabled is "Master Tickets".