7 ms·

what about something with a db? or auth?

• saulpw 28d ago
  I'm actually using Github issues as a low-volume/high-latency DB for a project right now. I use a Netlify function to do extremely simple auth and then open an issue on Github, which triggers a CI action, which appends to a .jsonl file in the repo (different branch), which triggers a Netlify build, which then serves the new jsonl file. (If the repo were public, this wouldn't even have to trigger a rebuild of the website, it could just get the .jsonl from Github directly). It's totally hack-a-licious but it also totally works for my N<10 users.
  • sakuraiben 28d ago
    Wow that's super cool and creative. I assume this is an internal dev tool?
    • saulpw 28d ago
      It's for a personal link bookmark site[0]. And I guess I had made the repo[1] public after all. It's been working well for about 6 months now. [1] https://github.com/saulpw/trove/ https://github.com/saulpw/trove/ [0] https://trove.saul.pw/ https://trove.saul.pw/