First class support for creating production bundles
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 927
- Forks
- 111
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
A good point was brought up in the announcement post on Lobsters - that while Hermit solves consistent tooling across workstation and CI, it doesn't for deploys. I suggested a couple of workarounds in that thread, but it would be nice for Hermit to provide direct support.
I'm not sure what that would look like in practice? Maybe:
hermit bundle --os=<os> --arch=<arch> <dest> <pkg> [<pkg> ...]
This could create a self-contained tgz or directory with the specified packages and dependencies, bin symlinks, and an activate.sh with all the uninterpolated envars, that does not rely on Hermit at all for runtime.
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
The issue names no implementation files or tests; start by tracing the proposed hermit bundle entry point and reviewing how packages, dependencies, symlinks, and activate.sh are currently assembled. Done should be defined as a self-contained tgz or directory that runs without Hermit at runtime, including the requested packages and dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, shell
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100