You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+81-35Lines changed: 81 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,33 +23,14 @@ Note: If you're using Linux Bash for Windows, [see this guide](https://www.howto
23
23
24
24
Sample configuration file provided in `sample.env`
25
25
26
-
-`WIW_API_TOKEN=when-i-work-login-token`
27
-
28
-
Sets the login token for the When I Work API. Necessary to load any data from When I Work.
29
-
30
-
-`WIW_API_URL=https://api.wheniwork.com/2/`
31
-
32
-
Base URL for When I Work's API. Shouldn't change too much.
33
-
34
-
-`EMS_API_USER=username`
35
-
36
-
Username to pass to EMS for accessing the API.
37
-
38
-
-`EMS_API_PASS=password`
39
-
40
-
Password to pass to EMS for accessing the API.
41
-
42
-
-`EMS_API_URL=https://base.url/EMSAPI/`
43
-
44
-
Root URL for the EMSAPI.
45
-
46
-
-`NOTES_TITLE_SEPARATOR=-`
26
+
#### Layout and Display Settings
47
27
48
-
Titles for events are in the notes for shifts in When I Work for our particular environment. This is subject to change, and thus the separator can be configured. Works in concert with `SEPARATOR_WHITESPACE`.
28
+
-`DISPLAY_PX_X=1920`
29
+
-`DISPLAY_PX_Y=1080`
49
30
50
-
-`SEPARATOR_WHITESPACE=true`
51
-
52
-
Configures whether or not the separator is surrounded by whitespace or not. In this example the above separator would be a dash surrounded by whitespace.
31
+
Optional. Device-specific Display specification. Used when creating the display window to ensure
32
+
it's the appropriate size for the attached display. Only needed if the machine cannot determine the
33
+
display dimensions on it's own.
53
34
54
35
-`MAX_REFRESH_INTERVAL=300`
55
36
@@ -63,6 +44,7 @@ Sample configuration file provided in `sample.env`
63
44
- LABOR = When I Work Labor (condensed view)
64
45
- EVENTS = When I Work labor events associated with an event
65
46
- EMS-EVENTS = Events scheduled in EMS (regardless of labor assignment)
47
+
- MZV-EVENTS = Events scheduled in Mazevo
66
48
67
49
When both Left and Right render modes are the same, the screen will render data across both columns (top to bottom, left to right). When the settings are different, each column will render it's data in the set column only (top-to-bottom).
68
50
@@ -75,6 +57,16 @@ Sample configuration file provided in `sample.env`
75
57
76
58
Sets the display title in the corner of the screen. Defaults to 'Events Display'.
77
59
60
+
#### API Data Source: When I Work
61
+
62
+
-`WIW_API_TOKEN=when-i-work-login-token`
63
+
64
+
Sets the login token for the When I Work API. Necessary to load any data from When I Work.
65
+
66
+
-`WIW_API_URL=https://api.wheniwork.com/2/`
67
+
68
+
Base URL for When I Work's API. Shouldn't change too much.
69
+
78
70
-`WIW_API_LOCATION=123456`
79
71
80
72
API Location ID to search When I Work for shift data. Can be set to a comma-delimited list, such as `123456,234567,345678` to get shifts for multiple locations at once.
@@ -83,30 +75,82 @@ Sample configuration file provided in `sample.env`
83
75
84
76
How many days worth of data to query from the API each time. Defaults to 7.
Naming to differentiate When I Work locations from each other when using the 'LABOR' layout, which has shifts in a condensed form.
81
+
82
+
-`NOTES_TITLE_SEPARATOR=-`
83
+
84
+
Titles for events are in the notes for shifts in When I Work for our particular environment. This is subject to change, and thus the separator can be configured. Works in concert with `SEPARATOR_WHITESPACE`.
85
+
86
+
-`SEPARATOR_WHITESPACE=true`
87
+
88
+
Configures whether or not the separator is surrounded by whitespace or not. In this example the above separator would be a dash surrounded by whitespace.
89
+
90
+
#### API Data Source: EMS
91
+
92
+
-`EMS_API_USER=username`
93
+
94
+
Username to pass to EMS for accessing the API.
95
+
96
+
-`EMS_API_PASS=password`
97
+
98
+
Password to pass to EMS for accessing the API.
99
+
100
+
-`EMS_API_URL=https://base.url/EMSAPI/`
101
+
102
+
Root URL for the EMSAPI.
103
+
86
104
-`EMS_LOOKAHEAD_DAYS=5`
87
105
88
106
How many days worth of data to query from the API each time. Defaults to 7.
89
107
90
108
-`EMS_BUILDINGS=1,2,3,4`
91
109
92
-
Building IDs in EMS to gather booking / event data for.
110
+
Building IDs in EMS to gather booking / event data for. Comma-separated, no whitespace.
93
111
94
112
-`EMS_STATUSES=2,3,4,5`
95
113
96
-
Status IDs in EMS to gather booking / event data for.
114
+
Status IDs in EMS to gather booking / event data for. Comma-separated, no whitespace.
97
115
98
116
-`EMS_EVENT_TYPES=1,2,3,4,5,6,7,8,9`
99
117
100
-
Event Type IDs in EMS to gather booking / event data for.
118
+
Event Type IDs in EMS to gather booking / event data for. Comma-separated, no whitespace.
Set row highlight colors (HEXA) (hex w/ alpha) associated event status ID (ID first). Applies to EMS event date list only. Separate each state setting from the color value by commas (`,`). Separate status ID and color code by colons (`:`).
109
123
124
+
#### API Data Source: Mazevo
125
+
126
+
-`MZV_API_URL=https://mazevo_public_API_URL/api/`
127
+
128
+
Mazevo URL to gather data from.
129
+
130
+
-`MZV_API_KEY=somehexstring`
131
+
132
+
Mazevo API Key. Generated on the Mazevo Web console.
133
+
134
+
-`MZV_LOOKAHEAD_DAYS=5`
135
+
136
+
How many days worth of data to query from the API each time. Defaults to 7.
137
+
138
+
-`MZV_BUILDINGS=1,2,3,4`
139
+
140
+
Building IDs in Mazevo to gather booking / event data for. Comma-separated, no whitespace.
141
+
142
+
-`MZV_STATUSES=2,3,4,5`
143
+
144
+
Status IDs in Mazevo to gather booking / event data for. Comma-separated, no whitespace.
145
+
146
+
-`MZV_EVENT_TYPES=1,2,3,4,5,6,7,8,9`
147
+
148
+
Event Type IDs in Mazevo to gather booking / event data for. Comma-separated, no whitespace.
149
+
150
+
-`MZV_ROOMS=1,24,86`
151
+
152
+
Room IDs from Mazevo to gather booking / event data for. Comma-separated, no whitespace.
153
+
110
154
## Updates
111
155
112
156
Dependency updates: update the base image in `Dockerfile` and update application dependencies in `package.json`.
@@ -133,21 +177,23 @@ Use Ensure files are up to date and that you are on the correct code branch. Run
133
177
2. Log into the Balena console with `balena login`
**Note(s):** Don't forget the trailing `.` which designates the current directory as the source for the code. Substitute in the name of your fleet for `[BALENA FLEET NAME]` which corresponds to the application name on the Balena Cloud dashboard. Add `--logs` to see the complete build details. For complete CLI documentation and other options see the [Balena CLI documentation][2].
139
183
140
184
4. Push the built image to Balena Cloud
141
185
142
186
> `balena deploy [BALENA FLEET NAME]`
143
187
144
-
### Building with Balena Cloud
188
+
### Building with Balena Cloud (Recommended)
189
+
190
+
This method tends to be more reliable and avoids local problems dependent on docker desktop being installed.
145
191
146
192
1. Open a console to the project root (where `Dockerfile.template` and `package.json` are)
147
193
2. Log into the Balena console with `balena login`
148
194
3. Push code to Balena's build servers and wait for the image to be deployed automatically
0 commit comments