suggest
coolify
suggest | coolify | |
---|---|---|
2 | 113 | |
14 | 16,289 | |
- | 25.4% | |
3.6 | 10.0 | |
10 months ago | about 11 hours ago | |
Nim | PHP | |
ISC License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
suggest
-
Self Hosted SaaS Alternatives
You are welcome. Thanks are too rarely offered. :-)
You may also be interested in word stemming ( such as used by snowball stemmer in https://github.com/c-blake/nimsearch ) or other NLP techniques, but I don't know how internationalized/multi-lingual that stuff is, but conceptually you might want "series of stemmed words" to be the content fragments of interest.
Similarity scores have many applications. Weights on graph of cancelled downloads ranked by size might be one. :)
Of course, for your specific "truncation" problem, you might also be able to just do an edit distance against the much smaller filenames and compare data prefixes in files or use a SHA256 of a content-based first slice. ( There are edit distance algos in Nim in https://github.com/c-blake/cligen/blob/master/cligen/textUt.... as well as in https://github.com/c-blake/suggest ).
Or, you could do a little program like ndup/sh/ndup to create a "mirrored file tree" of such content-based slices then you could use any true duplicate-file finder (like https://github.com/c-blake/bu/blob/main/dups.nim) on the little signature system to identify duplicates and go from path suffixes in those clusters back to the main filesystem. Of course, a single KV store within one or two files would be more efficient than thousands of tiny files. There are many possibilities.
-
SymSpell: 1M times faster spelling correction
As jamra correctly points out, the entry point to this (which gets a lot of traction on HN) is indeed attacking a strawman tutorial-written-on-an-airplane algorithm. So, the 1M speed-up is majorly over-hyped.
That said, the technique is not wholly without merit, but does carry certain "risk-reward" trade offs related to latency in the memory/storage system because of SymSpell's reliance upon large hash tables. For details see https://github.com/c-blake/suggest
coolify
- Open-source alternative to Heroku, Vercel, and Netlify
-
Deploy SvelteKit with SSR on Coolify (Hetzner VPS)
This is my first quick try deploying SvelteKit with the open source software Coolify by Andras Bacsai.
-
Standalone Next.js. When serverless is not an option
With a serverful approach, you can avoid these drawbacks, and the main challenge lies in selecting the platform that aligns with your requirements. Options may include AWS, Render, DigitalOcean, and others. While VPS is also an option, it's generally not recommended due to the significant setup and maintenance overhead involved (logging, monitoring, CI/CD pipelines, etc.). However, you can make your life easier by leveraging tools like Coolify that help managing your VPS.
-
Let's build a screenshot API
Heroku and similar providers can simplify the server management issues, but you can use something much better that can combine both cost efficiency and ease of deployment—Coolify:
-
Quantum alternatives - coolify and meli
3 projects | 12 Mar 2024
-
Serverless Horrors
> VPSs being “easy to manage” is a strong option full of assumptions.
There are definitely many footguns with managing a VPS but I think the threshold to get vaguely competent with a VPS is not really that far off with getting familiar with the average cloud platform - which comes with its own dangers, like the near-total inability to put an upward cap on fees that that person found out with Netlify recently.
Having a $5 VPS and knowing it's never going to cost your more than $5 might balance out a lot of things on the other side for a lot of people.
(And, as a bonus, it comes with the benefit of having a better idea of what is going on on the actual computer which is running your code.)
Platforms like https://coolify.io/ (which I have not tried, but looks interesting) seem to give you some of the abstractions that you get in cloud platforms to save you having to mess with too much low level stuff and become an expert in a billion separate systems.
If you have Debian with automatic updates that does most of the heavy lifting for you. The hardest problem I have is resisting the temptation to just install everything, because the cost to do it is capped at my VPS monthly fee.
So yep, it comes with a lot of assumptions. But so does everything!
-
Netlify just sent me a $104K bill for a simple static site
https://coolify.io/ might be worth a look
-
The 2024 Web Hosting Report
The modern iteration of these tools has taken the developer experience learnings from the Platform as a Service (PaaS) category, and will bring them to your own VM, giving you your own personal PaaS. Example of this include Dokku, Coolify, Caprover, Cloud66 and many more!
- Coolify – Self-Hostable PaaS
- Open-source and self-hostable Heroku/Netlify alternative
What are some alternatives?
nimsearch - A nascent tutorial/intro to search engine ideas in Nim
CapRover - Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids
abydos - Abydos NLP/IR library for Python
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
ordiri
porter - Kubernetes powered PaaS that runs in your own cloud.
jsymspell - Java 8+ zero-dependency port of SymSpell: 1 million times faster through Symmetric Delete spelling correction algorithm
meli - Platform for deploying static sites and frontend applications easily. Automatic SSL, deploy previews, reverse proxy, and more.
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
Empire - Empire is a PowerShell and Python post-exploitation agent.
core - OPNsense GUI, API and systems backend
pack - CLI for building apps using Cloud Native Buildpacks