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
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,11 +112,13 @@ in both file types (dynamic served and services), you can use all node/bun metho
112
112
-`service_require(service path)`: returns the matching service object
113
113
-`service_require_try(service path)`: returns the matching service object or null if not found or if disabled
114
114
-`rtjscomp`: has these properties/methods:
115
-
-`actions`: an object with methods for server control (http[s]_[start|stop|kill], log_clear, halt, exit)
115
+
-`actions`: an object with methods for server control (http[s]_[start|stop|kill], log_clear, file_watch_force_all, halt, exit)
116
116
-`async data_load(path)`: reads the file in data directory and returns its content or null
117
117
-`async data_load_watch(path, callback(content))`: executes callback first and on every change
118
118
-`async data_save(path, content)`: writes the content to the file in data directory
119
119
120
+
most file updates are handled automatically, but some updates cannot be detected, for example by git, so you can force a reload of all files by calling `rtjscomp.actions.reload_force()` or sending a `SIGHUP` signal to the process (done by systemctl reload).
121
+
120
122
## environment variables
121
123
-`rtjscomp_path_data`: path to data directory, default is `./data`
122
124
-`rtjscomp_path_public`: path to public directory, default is `./public`
0 commit comments