Skip to content

Commit ea9018f

Browse files
committed
[skip-ci] remove roadmap section
1 parent f3595a5 commit ea9018f

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

README.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -116,20 +116,6 @@ This would pass the environment variable `MOUNT_POINT=/data` to the `docker-comp
116116
have a bunch of compose configs that all mount data to some path on the machine, you then use
117117
`${MOUNT_POINT}/postgres:/var/lib/postgres/data` as a volume declaration in your `docker-compose.yml`.
118118

119-
## Roadmap
120-
121-
The current implementation is an MVP that does one thing well, but there some features I'd like to implement in future
122-
to ease the maintenance and user experience:
123-
124-
- Daemon control - currently, `wadsworth run` will just run and block until it is killed, I would like to provide a way
125-
to interact with a running instance of `wadsworth` via a Unix socket file and a simple API (similar to Docker). This
126-
would open up the ability to perform forced triggers of targets or disable certain targets via the command line.
127-
- Proper releases - Right now you grab the binary and run it, how you daemonise it is up to you. I'd like to provide a
128-
systemd unit file and a Snapcraft app for easier installation and usage.
129-
- Dependency Tree - this is a maybe but it could be useful if all repos are both config repos and target repos. In other
130-
words, every repo can contain `.js` config files to build a dependency tree of repos. But I'm not sure if there's a
131-
use-case for this yet (or ever).
132-
133119
[wadsworth]: https://i.imgur.com/RCYbkiq.png
134120
[git-ops]: https://www.weave.works/blog/gitops-operations-by-pull-request
135121
[kube-applier]: https://github.com/box/kube-applier

0 commit comments

Comments
 (0)