Re:Show HN: SQLSite – serve simple websites, APIs and files ...
by CyberFonic on Thursday January 16, 2020 @03:49PM
(#22068737)
I too wrote something similar in Python a couple of years ago. BUT that's not the point. Your contribution is well documented and effectively shared with whomever might want to use it. That is of value to our community.
Re:Show HN: SQLSite – serve simple websites, APIs and files ...
by tracker1 on Thursday January 16, 2020 @05:52PM
(#22069934)
A few years ago, worked on something similar with Node, Redis and Cassandra... depending on the type of data a given site/resource was, it would either deliver the static content, or run a given node module/version to process and deliver the request... worked very well at scale.
Re:Show HN: SQLSite – serve simple websites, APIs and files ...
by j4mie on Friday January 17, 2020 @03:29AM
(#22072898)
That's exactly what it does do! Everything is served from the sqlar table inside the database. Is there a bit of the documentation that doesn't make that clear?
Re:Show HN: SQLSite – serve simple websites, APIs and files ...
by paparush on Thursday January 16, 2020 @02:28PM
(#22067941)
Maybe I'm missing something. I built a website and hand-rolled cms ten years ago leveraging PhP and SQLite that stores and serves the site and certainly allows full CRUD operations.
Project Page: https://h3rald.com/litestore/
User Guide: https://h3rald.com/litestore/LiteStore_UserGuide.htm
This might be a good alternative.
Suggestion: First class serverless/S3 support perhaps?
This also reminds me of how crt.sh runs primarily off Postgres: https://github.com/crtsh
Question: why not put everything into the SQLite DB as opposed to files next to the db in an archive?