This repository was archived by the owner on Oct 6, 2026. It is now read-only.
Repository navigation
DAWGit 0.13.3
Pre-release
Pre-release
Work in progress. DAWGit is an early preview for Windows, tested with Ableton Live 12. Expect rough edges and changes before 1.0.
Stable and Nightly
- DAWGit now comes in two channels from the same app: Stable (tested releases, Ableton Live projects) and Nightly (the newest build, with what is still in testing: Unity, Unreal, code and design projects). Switch in Settings › Updates › Channel. Moving to Nightly offers its latest build right away; moving back to Stable keeps the Nightly until a Stable release is newer.
- A Stable build opening a Unity or Unreal project says it needs Nightly instead of not knowing it.
- Teams with Stable and Nightly members stay safe: a feature that changes what a team stores is turned on per team, and a DAWGit without it stops before working with that team (and says to update).
- DAWGit Pro users: on a first start without settings of its own, DAWGit takes DAWGit Pro's (teams, keys, project locations) on the Nightly channel.
Safer storage
- Branch log: every move of a team's branch (a share, a merge, a branch made or deleted) is recorded — who, when, from which version to which.
dawgit branch log [NAME]shows it, to put back a branch moved by mistake. - Cleanup trash: storage cleanup no longer deletes unused files outright; they go to a trash in the storage for two weeks. Should a cleanup ever be wrong, DAWGit takes a file back from there when it's needed (and
dawgit verify --repairdoes for a whole project). - Settings and team records written by a newer DAWGit keep the parts an older one doesn't know when the older one saves them (Stable and Nightly share them).
- Changes to DAWGit's settings from the app, the command line and background work (backups, setup sharing) no longer overwrite each other.
- Every connection to a team checks the team's features, joining and creating a team included.
Help
- Log files: the app now keeps a log (Settings › Help › Log files), with keys and connection codes left out, to attach to a bug report. A crash is written there too.
Under the hood
- Storage is built in two layers (key storage below, everything a team stores above), tested to survive a share cut off at every single step.
- The self-hosted team server (
dawgit serve) keeps working but gets no new features; team storage (R2, S3) is the way forward.