trufnetwork / trufnetwork/node
Goal: have TN docker images in gh packages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
Description
It's a very low-hanging fruit, and could improve maintainability and deployability on other repos, tests, node operators setup, etc
- At release gh action, also deploy a trufnetwork/node image to gh container registry
this should publish what we have at https://github.com/trufnetwork/node/blob/main/deployments/Dockerfile, no more than it
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 deployments/Dockerfile and the repository's release GitHub Action. Check how releases currently build and publish artifacts, then connect that flow to publish trufnetwork/node as a GitHub Container Registry image. Done means the release action publishes the Docker image and the existing Dockerfile is used unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100