Building CRUD with htmx
The Stack (original)
Going to use the following
frontend:
- htmx
backend:
- golang / fiber for the language and server
- fig for configuration
- clover for the database
The Repo
Going to have a publicly hosted repo over at github.
Description of the project
The project is just going to be a little pet project that I can experiment with. For fun and for this blog ill breakdown each of the development steps as I run into them.
The origin
Started out by looking at a few articles and even seeing what chatGPT would say in terms of what the file structure should look like. Much like salt, ive been blown away with the variety of approaches for golang file hierarchy.
I left the chatGPT resource out of it because it kinda failed hilariously which may have just been the issue of the LLM model ending in 2021. Who knows, but deep inside I my breathing relax. For much like death, AI isn’t taking my job today.
I really liked the quii todo css style and the static file layout. Felt like MVC was making a come back, but I wasn’t as big of a fan towards moving everything into a domain directory so I kinda went and reworked the ideas from petstore app.
Side note
Im also not super sure that Clover is going to be the end all goal. I started fiber with the prefork option to true which meant that SO_REUSEPORT was enabled. Which is amazing, if you want to know more I think Fenny said it best here, but that has some straight issues with the way im working with clover as a data source. So I may need to see what client pooling is available for a critical section that is basically a singleton.
So one alternative I thought about was using the Solid Protocol. This would allow me to save off the rss feeds and basically get some free storage. It’s mostly just a thought at this point but could be fruitful in the future.
Second Day
Going to start building the actual pulling and parsing multiple rss feeds. So look forward to more soon.
