Where is the Terra source code? Nils Gehlenborg March 12, 2019 15:26 5 comments I am looking for the Terra source code. Where can I find that? Thanks! Nils Comments 5 comments Sort by Date Votes Brad Taylor March 12, 2019 15:38 Hi Nils, Terra shares it's backend with our existing system FireCloud. Terra/FireCloud's API is documented here: https://api.firecloud.org/ Python bindings for interacting with the API programmatically can be found here: https://github.com/broadinstitute/fiss Regarding the source code: Terra is powered by a suite of microservices, each of which is open source. I can provide the full list, but it might be helpful to understand what you're looking for. Are you interested in reading the code for information, making a contribution, or running your own instance? Deploying these services in coordinated fashion is currently fairly difficult. The source code for the Terra UI layer is here: https://github.com/DataBiosphere/saturn-ui 0 Nils Gehlenborg March 12, 2019 15:40 Thanks, Brad. I am looking for the full list of repositories that I would need to launch my own instance of Terra. Nils 1 Geraldine Van der Auwera March 12, 2019 23:00 Hi Nils, we don't currently have that documented in a single place but I'll add that to the documentation team's todo list. To be frank though, just the list of repos won't be sufficient for what you're trying to do. We're currently exploring solutions for making it realistic for a third party to launch an independent instance of Terra, because that is definitely something we want to enable, but we're not quite there yet. You can help us elevate the importance of this need -- and ensure we keep you in the loop as the situation progresses -- by turning this into a Feature Request. 0 Nils Gehlenborg March 13, 2019 15:27 Done. I created two separate requests: one for the list of repos (easy) and one for a deployment manual (probably not that easy). 0 Jack Warren June 23, 2023 13:57 (Terra DevOps here -- this ask came up internally, figure I'll answer here and on the feature requests too) The tricky part of this ask is that while the source code of the individual services is intentionally public, the configuration of how we run them and wire them together actually needs to be a bit more private. Our information security folks consider that a bit sensitive, to the point where we can't make that part public. What that means is that while I can actually get a list of source code repositories for the individual services pretty easily, it's really not enough to run your own Terra instance. There'd be a lot to figure out. Making a deployment manual is a good feature request in that light. Some of the reason that's difficult for us to prioritize is because we basically can't use our existing architecture to write the manual -- the existing architecture is what we can't publish, so we'd have to come up with an alternative way to deploy everything. Time we'd spend doing that is time we could spend improving the shared instance so folks wouldn't have to deploy their own. Here's the list of source code repositories for the individual services we currently run as part of Terra: https://github.com/DataBiosphere/bond https://github.com/DataBiosphere/consent https://github.com/DataBiosphere/consent-ontology https://github.com/DataBiosphere/duos-ui https://github.com/DataBiosphere/jade-data-repo https://github.com/DataBiosphere/job-manager https://github.com/DataBiosphere/leonardo https://github.com/DataBiosphere/terra-billing-profile-manager https://github.com/DataBiosphere/terra-drs-hub https://github.com/DataBiosphere/terra-ui https://github.com/DataBiosphere/terra-workspace-manager https://github.com/broadinstitute/agora https://github.com/broadinstitute/cromwell https://github.com/broadinstitute/firecloud-orchestration https://github.com/broadinstitute/firecloud-ui https://github.com/broadinstitute/import-service https://github.com/broadinstitute/martha https://github.com/broadinstitute/rawls https://github.com/broadinstitute/sam https://github.com/broadinstitute/thurloe 0 Please sign in to leave a comment.