micro-editor / micro-editor/micro
Distribution with DotSlash?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
DotSlash is a distribution utility by Meta which I would like to use for micro. It is designed to be used by checking in a declarative file pointing at a binary into a repository, and this file can be used transparently by any user to invoke the binary. I would like to use this to bring with me micro to all the machines I use.
In slightly more detail, DotSlash uses a JSON file mapping host platforms (such as linux-x86_64 and macos-aarch64) to several key items, including the URL to a release archive, a secure hash of this file and the path to the executable binary inside this archive. DotSlash is then used to transparently execute the binary based on this specification, and it will download and store the binary locally automatically, as needed.
I can create such a spec file manually myself. It could also be created as a part of release builds of micro, possibly by utilizing the reusable dotslash-publish-release GitHub action. If a dotslash-file were distributed with micro, it would make upgrading easier for me, and it would enable a new distribution channel for more people.
Thanks for micro ❤️ and thanks for considering 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 with the linked DotSlash documentation and the reusable dotslash-publish-release GitHub Action. Determine how micro's release builds could produce and distribute a DotSlash specification covering the supported host platforms. Done means users can obtain the specification with micro releases and use it to download and run the appropriate binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100