A full-stack web app (database back end and non-static front-end) hosted entirely on GitHub Pages / Actions.
What ??!? Does this really host a full stack SQLite app on GitHub Pages/Actions only?!?!
- The Guestbook
Yes. Obviously it's not ideal, but it's the only way I could think to do it. The token lets us trigger the workflow. When we trigger it we can pass data to it. That data is then sanitized and written into the database. That creates our whole "serverless backend." The token is scoped to this repo only, and to actions of this repo only.
The ROT13 is necessary to prevent GitHub auto-detecting an "exposed" token and immediately expiring it.
That is done by using single quotes in the SQL insert statement to cause the values to be escaped, and using the "sanitize-html" library.