vectordotdev / vectordotdev/vector
Document how to produce release artifacts locally from source
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Following https://github.com/timberio/vector/pull/2239#pullrequestreview-388557845, it would be nice to have documented on the website (for example, installation from source page) how to produce all kinds of release artifacts for Linux (such as archives, DEB and RPM packages, and Docker images) locally.
Contributor guide
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 website's installation from source page linked in the issue and review how the project produces Linux release artifacts. Document local production of archives, DEB and RPM packages, and Docker images from source; the page is complete when these artifact types and their local-generation steps are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, rust
- Domain
- build-system, documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100