railsdiff.org was really helpful to upgrade in addition to the official documentation, especially now with LLMs that can process all these text and assist you in the process.
274 karma · joined December 22, 2017
railsdiff.org was really helpful to upgrade in addition to the official documentation, especially now with LLMs that can process all these text and assist you in the process.
As for the drivers compatible, if you mean "clients", in our case we use the official Python Redis client with Kvrocks and it works perfectly with the commands we use.
It looks like a normal database to me: disk storage for most of the data, and some cache in memory to speed up read queries. Everything is customizable.
I'm still waiting for a nice way to deploy it in a Kubernetes cluster, like a Helm Chart to easily setup a cluster with primaries and replicas. Also, the lack of keys eviction like LRU is problematic for us in some cases, it would be a nice addition.
For instance, Ffmpeg can do that with the filter `select=gt(scene,0.3)`. It selects the frames whose scene detection score is greater then 0.3 (the scene change detection score are values between 0 and 1).
We picked this project because of our RAM usage that was exploding with Redis.
The only downside for us right now is the Kubernetes support. There is an operator and a controller being made but no Helm Chart yet to deploy Kvrocks with master and replicas easily. That will be awesome.
Simple app but funny game.
[0]: https://github.com/TeamPiped/Piped
[1]: https://piped.video
It works great and the development is really active.
Something I like too (not sure if it exists somewhere else) is the ability to copy/paste an article (let's say from medium) directly in the WYSIWYG mode. You basically get your article just like it is being displayed on medium: h1 detected, paragraphs, bold etc. OOTB. Really nice.
The creator of Rails talks about it here: https://world.hey.com/dhh/modern-web-apps-without-javascript...
My main concerns though were about testing. What if you want to create tests to check if your scraper still gets the data we want? Colly allows nested scraping and it's easy to implement but you have all your logic into one big function, making it harder to test.
Did you find a solution to this? I'm considering switching to net/http + GoQuery only to have more freedom.
By the way, just discovered a nice library to test GitHub Actions locally: https://github.com/nektos/act
My bottle of 1 liter (33 oz I think in the US) lasts 4 or 5 days so I don't know if I'm at risk.