adoralaura/personal-website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

update erisi
All checks were successful
ci/woodpecker/push/deploy-netlify Pipeline was successful
Details

Browse source
This commit is contained in:
Adora Laura Kalb 2023-09-01 08:49:53 +02:00
parent e7ec373869
commit c0caaf8e47
Signed by: adoralaura
GPG key ID: 7A4552166FC8C056
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
content/projects/erisi.md
View file

@ -1,17 +1,17 @@
--- ---
title: "erisi: A self-hosted static site server" title: "erisi: A self-hosted static site server"
description: "Project outline page for erisi. erisi is planned to be a self-hosted alternative to Netlify/Vercel/Github Pages/etc... written in Go and utilizing Caddy and it's ACME capabilities." description: "Project outline page for erisi. erisi is planned to be a self-hosted alternative to Netlify/Vercel/Github Pages/etc. written in Go and utilizing Caddy and its ACME capabilities."
--- ---
## Summary ## Summary
`erisi` is planned to be a self-hosted alternative to Netlify/Vercel/Github Pages/etc... written in Go and utilizing [Caddy](https://caddyserver.com) and it's ACME capabilities. `erisi` is planned to be a self-hosted alternative to Netlify/Vercel/Github Pages/etc... written in Go and utilising [Caddy](https://caddyserver.com) and its ACME capabilities.
## Implementation Ideas ## Implementation Ideas
The main service will consist of a Caddy instance (maybe later replaced with own application loogic for subdomain handling, TLS termination and ACME) that serves as a HTTPS entry point and host for static website data. The main service will consist of a Caddy instance (maybe later replaced with its own application logic for subdomain handling, TLS termination, and ACME) that serves as an HTTPS entry point and host for static website data.
The `erisi` server will serve a registration/configuration page, where you can add new websites (like with netlify) and see what you need to do (in terms of CNAMEs and CAA-Records) to enable custom domains. It will then create directories per user and within per repository/website (think `/base-dir/user-guid/project-guid` as the path) and communicate (custom) domain to caddy. The `erisi` server will serve a registration and configuration page, where you can add new websites (like with netlify) and see what you need to do (in terms of CNAME- and CAA-Records) to enable custom domains. It will then create directories per user and therein per repository/website (think `/base-dir/user-guid/project-guid` as the path), and communicate the (custom) domain and webroot path to caddy.
There should also be a `erisi` cli application for deploying websites to the server. Maybe it should compress a given folder, hash it and send it to the server, handling authentication in the progress. There should also be an `erisi` cli application for deploying websites to the server. Maybe it should compress a given folder, hash it and send it to the server, handling authentication in the process.
Maybe later something like netlify's `netlify.toml` can be implemented to handle custom headers and redirects/rewrites :3 Maybe later something like netlify's `netlify.toml` can be implemented to handle custom headers and redirects/rewrites :3