Reducing number of binaries for peachcloud #57
Labels
No Label
bug
documentation
duplicate
enhancement
help wanted
invalid
maintenance
peach-lib
peach-network
peach-oled
peach-stats
peach-web
question
refactor
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: PeachCloud/peach-workspace#57
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
currently
... are each their own binary
... and each include peach-lib as a dependency (so thats a fair amount of duplicated code and extra MB)
could imagine re-modelling this, so that there is just one binary, that gets called in different ways.
e.g.
basically adding peach-web and peach-dyndns-updater as subcommands to what is currently peach-config (and renaming it peach). maybe there are also other ways.
however! I dont think we should do this now. I think we should focus on releasing something, using what's here. Just noting this as an idea, for one way we could go down from multiple binaries, to just one binary, that gets used in multiple ways.
using this setup, one could additionally imagine creating syntax sugar binaries, which are just 1 one line bash scripts, if desired... e.g.
peach-web (which calls peach web)
peach-config (which calls peach config)
etc. as desired. could even exactly mimic the current interfaces.
cc @glyph
Copied from #128 (comment)