31 Commits

Author	SHA1	Message	Date
zadam	192e399cb5	typos	2023-06-30 11:18:34 +02:00
zadam	64db5e2542	cleanup of app.js, wwww	2023-05-07 15:23:46 +02:00
zadam	8de67b6945	small fixes / refactoring	2023-03-12 21:37:13 +01:00
Сашка724ая	9a08aa2ab5	Fix healthcheck and some messages	2023-03-11 20:57:16 +11:00
Сашка724ая	02f218389b	support listening on unix sockets	2023-03-11 20:21:32 +11:00
zadam	6b4800d2d6	port error clarifications	2023-03-08 07:31:10 +01:00
zadam	1b24276a4a	always use template strings instead of string concatenation	2022-12-21 15:19:05 +01:00
zadam	261f1f0bf2	fix electron	2022-09-04 14:01:34 +02:00
zadam	8588ed5eec	remove port scanning for an available port #3036	2022-09-04 14:00:39 +02:00
zadam	f161488c13	focus existing window on port conflict, closes #3036	2022-09-04 14:00:34 +02:00
DynamoFox	912f79f1af	Add optional support to trust reverse proxies (via X-Forwarded-For)	2022-08-04 00:19:54 +02:00
zadam	28df5d4aa2	etapi improvements and more tests	2022-01-12 19:32:23 +01:00
zadam	91dec23d5e	ETAPI auth, spec improvements etc.	2022-01-10 17:09:20 +01:00
FliegendeWurst	6f49f870ed	Exit on SIGTERM (#1891) ... Stopping the systemd service running the server now works properly.	2021-04-25 11:05:09 +02:00
王登辉	138903cf28	fix config.ini Network host not work (#1546)	2021-01-18 17:46:48 +01:00
zadam	e2fcc6711a	style tweak of sidebar headers	2020-09-24 21:58:00 +02:00
zadam	07bd5129ca	similarity tweaks	2020-09-19 21:59:01 +02:00
zadam	88348c560c	syncification	2020-06-20 12:31:38 +02:00
zadam	28dc6b93ca	lock CPU info for perf context	2020-06-07 23:56:51 +02:00
zadam	cf6f04defb	better port error logging	2019-12-04 22:59:26 +01:00
zadam	36c87b7fa0	renamed "messagingService" to "ws"	2019-08-26 20:21:43 +02:00
Xavier NUNN	dcebcb0e73	Add host option (#588) ... * Added option to configure host * Updated sample config	2019-07-09 22:50:20 +02:00
Slavi Pantaleev	86b9f5a8b0	Exit on SIGINT ... Pressing Ctrl+C used to not exit the application (at least when running the Docker image). Explicitly catching the `SIGINT` interrupt signal and exiting fixes the problem. We currently make it exit immediately as soon as the signal arrives. In the future, it may be preferable to do dispatch some event and try to exit more gracefully (finish any ongoing synchronization work, etc.) Still, I think it's better to exit directly than to not do anything at all, in which case `SIGKILL` is likely to follow and kill the process even more abruptly.	2019-05-28 13:38:32 +03:00
zadam	83b4382787	missing cert and key error message	2019-04-08 20:08:29 +02:00
azivner	e211dd65ad	exit on detection of not supported node version, #324	2019-01-26 19:59:51 +01:00
azivner	9452fc236b	electron build uses random free port, fixes #142	2018-07-31 19:50:18 +02:00
azivner	fc6669d254	initialization and schema fixes, closes #111	2018-06-01 22:26:37 -04:00
azivner	e827ddffb9	electron fixes	2018-04-05 23:17:19 -04:00
azivner	26e4ad9bf9	separated DB initialization methods into sql_init	2018-04-02 21:25:20 -04:00
azivner	e2921a648d	refactored backend to use new naming convention for modules	2018-04-01 21:27:46 -04:00
azivner	52ad7f64b4	moved all sources to src directory	2018-01-28 22:18:15 -05:00