chore: update readme

This commit is contained in:
Asger Gitz-Johansen 2024-08-22 06:56:50 +02:00
parent 1d18e15b19
commit 4d9c1b2a2c
2 changed files with 5 additions and 0 deletions

View File

@ -73,6 +73,9 @@ Could this also be used as a systest replacement? The value of systest is the dr
really the controllers themselves. But yes, this system could replace the systest runner scripts. But not the drivers or really the controllers themselves. But yes, this system could replace the systest runner scripts. But not the drivers or
the configuration files themselves... the configuration files themselves...
Why trigger files instead of IPC (Inter Process Communication)?
It was easier to implement. If you know how to add POSIX IPC (not a fan of System-V IPC), please submit a PR :-)
### Using ### Using
`/etc/sci/conf.d/pipelines.conf` `/etc/sci/conf.d/pipelines.conf`
```txt ```txt

View File

@ -42,6 +42,8 @@ docker is super easy, just make a dockerfile - only concern is the trigger files
- [ ] I am deliberately not using `Restart=on-failure` in the `scid.service` file because we are using `Type=exec` - [ ] I am deliberately not using `Restart=on-failure` in the `scid.service` file because we are using `Type=exec`
and not `Type=notify` (yet) - which would require a `sd_notify` call of `READY=1` (see `man systemd.service`) and not `Type=notify` (yet) - which would require a `sd_notify` call of `READY=1` (see `man systemd.service`)
- [ ] Custom environment variables passed to the pipelines on invokation should be possible. - [ ] Custom environment variables passed to the pipelines on invokation should be possible.
- [ ] Listener threads should be killed and restarted (worker pool should just chug along) when pipeline config file
has changed during runtime. Should be disableable with `--no-hot-reload-config` - i.e. on by default.
### Note Regarding `inotify` usage ### Note Regarding `inotify` usage
From the manpage: From the manpage: