Move to self hosted runner
- Dominant language
- Markdown
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
running on github CI shows to be unreliable for testing connections (recently at least). I think the better way would be to move to some other network per https://upptime.js.org/docs/configuration/#self-hosted-runners howtos. @CodyCBakerPhD has experience with those. But ideally we do that on some DANDI centrally managed instance, not yet another use for an ad-hoc server (of mine). @kabilar @satra WDYT?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Upptime self-hosted runner documentation and review this repository's GitHub CI configuration. Identify a centrally managed DANDI instance or network suitable for the connection tests, then verify that the checks run reliably on the selected self-hosted runner instead of GitHub-hosted CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100