3 commits

Author	SHA1	Message	Date
Erin of Yukis	777a26f492	Add systemd-compatible service manager notification after bewCloud has successfully started (#137) ... * Add systemd-compatible service manager notification after bewCloud has successfully started * Use `systemd-notify` util instead of native integration while Deno APIs aren’t there yet * Implement different approach for systemd-notification reporting I went with a slightly different option, given I was struggling to lose a lot of flexibility in the original listening log (because it's started with some server state parameters) or allow so much unnecessary/duplicate complexity from Fresh in `fresh.config.ts` because I'll probably eventually ditch it (given #99). Some relevant references in the original `fresh` code: - ab14d1044c/docs/1.x/concepts/server-configuration.md (L207-L208) - d9764e2005/src/server/config.ts (L95) - d9764e2005/src/server/mod.ts (L115-L118) - d9764e2005/src/server/boot.ts (L52-L57) * Remove unnecessary comments --------- Co-authored-by: Bruno Bernardino <me@brunobernardino.com>	2026-01-02 10:15:25 +00:00
Bruno Bernardino	e337859a22	Implement a more robust Config (#60) ... * Implement a more robust Config This moves the configuration variables from the `.env` file to a new `bewcloud.config.ts` file. Note that DB connection and secrets are still in the `.env` file. This will allow for more reliable and easier personalized configurations, and was a requirement to start working on adding SSO (#13). For now, `.env`-based config will still be allowed and respected (overriden by `bewcloud.config.ts`), but in the future I'll probably remove it (some major upgrade). * Update deploy script to also copy the new config file	2025-05-25 15:48:53 +01:00
Bruno Bernardino	a5cafdddca	Make it public!	2024-03-16 08:40:24 +00:00