SpikeInterface / SpikeInterface/spikeinterface-dockerfiles
Feature discussion: Automatic Image generation and deployment
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Feature idea: a script that automatically generates and builds docker files for use with spikeinterface.
Use case:
- Automatic updating and versioning of spikesorters as they compile. For currently there are two images for kilosort4 when there have been 8 releases.
I think it would be useful to able to specify the exact version of a package someone might've used at a time and replicated it. I am open to thoughts on this idea.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository’s existing Dockerfiles and the available Kilosort4 images, then compare how package and sorter versions are currently represented. The issue does not name an entry point or test; clarify the version source, generation workflow, and reproducibility requirements before implementation. Done would include automated image generation, building, and exact-version selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100