[GH-ISSUE #387] Create a JSON file to manage package versions for updates #247

New issue

Open

opened 2026-03-03 11:14:17 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 11:14:17 +03:00

Owner

Originally created by @manikanta9176 on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/387

Originally assigned to: @akhil-naidu, @pavanbhaskardev, @manikanta9176 on GitHub.

Summary

Create a centralized JSON file that defines and fixes the versions of all third-party packages used across the project, including beszel (hub and agent), netdata, dokku, buildkit, railpack, dokku plugins, and others.

Motivation

Managing package versions manually can lead to inconsistencies and unexpected behavior across servers. A single JSON file will allow us to:

Fix and track versions for all dependencies in one place.
Simplify the update process for all servers by updating the JSON file when releasing updates.
Enable automated update mechanisms (either triggered by release or user action) to use the JSON file as the authoritative source for package versions.

Acceptance Criteria

Create a JSON file listing all relevant packages and their versions.
Implement logic to update servers based on the versions specified in the JSON file.
Document the update process for maintainers and users.
Ensure future releases only require updating the JSON file to propagate new versions.

Additional Context

This feature will provide greater reliability and efficiency for both maintainers and users when updating server environments.

Packages to include (not exhaustive):

beszel (hub and agent)
netdata
dokku
buildkit
railpack
dokku plugin versions
Any other relevant packages

Please discuss additional package candidates and implementation details as needed.

Originally created by @manikanta9176 on GitHub (Aug 7, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/387 Originally assigned to: @akhil-naidu, @pavanbhaskardev, @manikanta9176 on GitHub. ## Summary Create a centralized JSON file that defines and fixes the versions of all third-party packages used across the project, including beszel (hub and agent), netdata, dokku, buildkit, railpack, dokku plugins, and others. ## Motivation Managing package versions manually can lead to inconsistencies and unexpected behavior across servers. A single JSON file will allow us to: - Fix and track versions for all dependencies in one place. - Simplify the update process for all servers by updating the JSON file when releasing updates. - Enable automated update mechanisms (either triggered by release or user action) to use the JSON file as the authoritative source for package versions. ## Acceptance Criteria - [ ] Create a JSON file listing all relevant packages and their versions. - [ ] Implement logic to update servers based on the versions specified in the JSON file. - [ ] Document the update process for maintainers and users. - [ ] Ensure future releases only require updating the JSON file to propagate new versions. ## Additional Context This feature will provide greater reliability and efficiency for both maintainers and users when updating server environments. Packages to include (not exhaustive): - beszel (hub and agent) - netdata - dokku - buildkit - railpack - dokku plugin versions - Any other relevant packages Please discuss additional package candidates and implementation details as needed.

kerem added the

feature

label

2026-03-03 11:14:17 +03:00

kerem commented

2026-03-03 11:14:18 +03:00

Author

Owner

@pavanbhaskardev commented on GitHub (Oct 1, 2025):

Here're the list of packages we're using in dflow:

Private Network

tailscale -> latest

Proxy

traefik -> v3.4
config-generator(ghcr.io/dflow-sh/config-generator) -> latest

Application

dflow-app(ghcr.io/dflow-sh/dflow) -> latest
mongodb -> 7
redis -> 7

Customer Machine Software

Application Management

dokku -> 0.35.15

Monitoring

beszel-hub(henrygd/beszel) -> latest
beszel-agent(henrygd/beszel-agent) -> 0.12.3
netdata -> latest

Build Tools

railpack -> latest
buildkit(moby/buildkit) -> latest
buildpacks(https://github.com/dokku/buildpack-nginx.git) -> latest
Backups
restic(mazzolino/restic) -> latest

@pavanbhaskardev commented on GitHub (Oct 1, 2025): Here're the list of packages we're using in dflow: ### Private Network 1. tailscale -> latest ### Proxy 1. traefik -> v3.4 2. config-generator(ghcr.io/dflow-sh/config-generator) -> latest ### Application 1. dflow-app(ghcr.io/dflow-sh/dflow) -> latest 2. mongodb -> 7 3. redis -> 7 ### Customer Machine Software Application Management 1. dokku -> 0.35.15 Monitoring 1. beszel-hub(henrygd/beszel) -> latest 2. beszel-agent(henrygd/beszel-agent) -> 0.12.3 3. netdata -> latest Build Tools 1. railpack -> latest 1. buildkit(moby/buildkit) -> latest 3. buildpacks(https://github.com/dokku/buildpack-nginx.git) -> latest **Backups** 1. restic(mazzolino/restic) -> latest