Skip to content

Commit a4e1a87

Browse files
committed
Added notification example
1 parent 6344bf8 commit a4e1a87

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

README.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,23 @@ adc.sh config -f
2727
A simple work flow example is listing, exporting and deleting a dashboard:
2828

2929
```
30-
adc dashboard list
31-
adc dashboard export 13
32-
adc dashboard delete 13
30+
adc.sh dashboard list
31+
adc.sh dashboard export 13
32+
adc.sh dashboard delete 13
33+
```
34+
35+
Another example is getting a notification while your on premise controller is starting up. Combine adc.sh with the notification tool of your choice ([noti](https://github.com/variadico/noti/), [terminal-notifier](https://github.com/julienXX/terminal-notifier), ...) or run commands after the controller is running:
36+
37+
```
38+
noti adc.sh controller isup
39+
adc.sh controller isup | terminal-notifier
40+
adc.sh controller isup ; adc.sh applications list
3341
```
3442

3543
Also, you can use `adc.sh` to easily create custom events, like code deployments:
3644

3745
```
38-
./adc.sh event create -s INFO -c "This release fixes some minor issues with the mini cart functionality" -e APPLICATION_DEPLOYMENT -a 145 "Version 3.5.1 released"
46+
adc.sh event create -s INFO -c "This release fixes some minor issues with the mini cart functionality" -e APPLICATION_DEPLOYMENT -a 145 "Version 3.5.1 released"
3947
```
4048

4149
If a certain API call is not yet wrapped into a command, you can use `controller call` as general interface:

0 commit comments

Comments
 (0)