Resource Factory is a universal approach to originating, refining, and rendering Markdown, HTML, type-safe SQL, or other assets that could comprise static sites or engineering artifacts.
GNU Affero General Public License v3.0
0
stars
3
forks
source link
Switch from custom / simple-http-server web serving to Caddy #67
Instead of having multiple services for sandbox (Deno) vs. dev (simple-http-server) vs. production (Traefik) we should moved to a unified Caddy-based strategy:
[ ] Switch from Deno pubctl.ts experimental / sandbox model to deno_fcgi via Caddy with spawn-fcgi/FCGI::Spawn for serving hot-reloadable / watchable builds
[ ] Switch from simple-http-server to Caddy (see config hints for configuring spawn-fcgi).
[ ] Add a caddy parameter to pubctl.ts (similar to serve) that would generate a Caddyfile for execution after all other resources were created. This way no separate execution script is required.
[ ] Consider using Caddy in production with oAuth support instead of Traefik with oauth_proxy
[ ] Consider using Pglet approach to "micro apps" by integrating a single service point and then, similar to CGI or FastCGI, allowing applets to be created
Instead of having multiple services for sandbox (Deno) vs. dev (
simple-http-server) vs. production (Traefik) we should moved to a unified Caddy-based strategy:simple-http-serverto Caddy (see config hints for configuring spawn-fcgi).caddyparameter topubctl.ts(similar toserve) that would generate aCaddyfilefor execution after all other resources were created. This way no separate execution script is required.In case we need native websockets: