Feature discussion: Automatic Image generation and deployment

Open
#75 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, dockerfile
Domain
build-system, devops

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.

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.

Dominant language
Dockerfile
Stars
9
Forks
8
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SpikeInterface/spikeinterface-dockerfiles

All issues in SpikeInterface/spikeinterface-dockerfiles

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.