Our data.wikipathways.org site is currently on WMCS. We can keep running it there, and it's working fine for now, but if we keep it there, someone needs to be responsible for maintaining the infra, e.g., updating the OS and making sure the disk space doesn't all get filled up. If we don't want to do that, we can move it to either Toolforge or GH.
Toolforge wouldn't require any OS updates, but it could require updates to libraries we install. Also, Toolforge wouldn't require worrying about managing disk space.
If we move it to GH, note that I've already done some work on a proof of concept. This job already creates the JSON and SVG files with unified xref mappings. I also created this demo release, which matches our data.wikipathways.org release for March. (Note that the JSON/SVG job could bloat the size of this repo. If we want to make it as easy as possible for users to fork/clone this repo, we want to keep it small. Maybe we'd want to create another repo to hold that data, or we could upload it to dropbox or figshare?)
AlexanderPico
commented
1 year ago
Our data.wikipathways.org site is currently on WMCS. We can keep running it there, and it's working fine for now, but if we keep it there, someone needs to be responsible for maintaining the infra, e.g., updating the OS and making sure the disk space doesn't all get filled up. If we don't want to do that, we can move it to either Toolforge or GH.
Toolforge wouldn't require any OS updates, but it could require updates to libraries we install. Also, Toolforge wouldn't require worrying about managing disk space.
If we move it to GH, note that I've already done some work on a proof of concept. This job already creates the JSON and SVG files with unified xref mappings. I also created this demo release, which matches our data.wikipathways.org release for March. (Note that the JSON/SVG job could bloat the size of this repo. If we want to make it as easy as possible for users to fork/clone this repo, we want to keep it small. Maybe we'd want to create another repo to hold that data, or we could upload it to dropbox or figshare?)