Skip to content

Currents docker compose setups for self hosted and on-prem solutions

License

Notifications You must be signed in to change notification settings

currents-dev/docker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

History

34 Commits

Repository files navigation

Currents.dev Docker

Docker configurations for running Currents services.

Repository Structure

├── docs/ # User documentation (published to GitHub Pages) ├── on-prem/ # Self-hosted deployment using Docker Compose │ ├── scripts/ # Setup and generation scripts │ └── templates/ # Modular compose templates └── (future tools) # Additional Docker configurations may be added here 

On-Premises

For self-hosted Currents deployment, see the On-Prem documentation.

cd on-prem ./scripts/setup.sh docker compose up -d

Development

Releasing (On-Prem)

Releases are tied to Currents container image tags, which use date-based versioning: YYYY-MM-DD-NNN.

Release Process

  1. Update the image tag in on-prem/.env.example:

  2. Update the changelog in on-prem/CHANGELOG.md:

    • Move items from "Unreleased" to a new version section
    • Add release date and summary of changes
  3. Commit the release:

    git add on-prem/.env.example on-prem/CHANGELOG.md git commit -m "release: on-prem 2026-01-14-001"
  4. Create a git tag (namespaced for on-prem):

    git tag on-prem/2026-01-14-001
  5. Push:

    git push && git push --tags

Tag Format

Tags are namespaced by tool to allow for future additions:

ToolTag FormatExample
On-Premon-prem/YYYY-MM-DD-NNNon-prem/2026-01-14-001

List all on-prem releases:

git tag -l 'on-prem/*'

About

Currents docker compose setups for self hosted and on-prem solutions

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •  

Languages