fresh-strapi.deno.dev
endoflife.date
fresh-strapi.deno.dev | endoflife.date | |
---|---|---|
2 | 43 | |
42 | 2,222 | |
- | 4.1% | |
6.5 | 9.9 | |
9 months ago | 1 day ago | |
JavaScript | Ruby | |
GNU General Public License v3.0 or later | MIT License |
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.
fresh-strapi.deno.dev
- Ask HN: Those making $0/month or less on side projects – Show and tell
-
Ask HN: What would be your stack if you are building an MVP today?
Fresh, with Strapi to help bootstrap a backend, but eventually migrating all to Deno when the budgets permit.
https://github.com/Hyprtxt/fresh-strapi.deno.dev
This site uses the framework, but not Strapi: https://videopoker.academy
endoflife.date
-
End of Life of Technologies and Devices
> where you can see overlapped timelines when support ended
I tried to generate a visual timeline for a given page (https://github.com/endoflife-date/endoflife.date/pull/2859, has some screenshots), but it was limited to a single page (so you'd only see nokia devices at once for eg).
It turned out that it is too hard to generate clear charts with vague data. We often only know whether is device is supported or not (true/false, see comments about samsung below in this thread), and don't have clear release dates.
I'll get to it someday (PRs welcome), but it might not work for the usecase we want (picking phones) because data on mobiles is very vague.
repairability score -> sounds interesting, will file an issue and see. The hard part is that there's no clear identifiers for devices (SWID/CPE are just not good enough) for us to track this kind of data from elsewhere easily.
-
understanding Rails version maintenance policy?
Here's the PR where it was added by a user, "Based on a Rails core team member's comment"...
-
Pragmatic Versioning – An Alternative to Semver
A lot of the communications regarding End of Life for Support is done very effectively here: https://endoflife.date/
-
Maybe helpful: https://endoflife.date
https://endoflife.date (not mine)
-
Central Hardware Firmware versions?
a little similar to endoflife.date if anyone has ever come across it for Software versions?
-
You can serve static data over HTTP
We do this at https://endoflife.date API, and it works quite well.
-
python-eol: A package to check whether the python version you're using is beyond/close to end of life
I've created the `db.json` with the [end of life](https://endoflife.date/) api.
-
Ask HN: Most interesting tech you built for just yourself?
Something I've recently worked on is building an SQLite database of all the dependencies my organisation uses, which makes it possible to write our own queries and reports. The tool is all Open Source (https://dmd.tanna.dev) and has a CLI as well as the SQLite data.
Ive used it to look for software that's out of date (via https://endoflife.date), to find vulnerablilities (via https://osv.dev) and get license information (via https://deps.dev)
It's been hugely useful for us understanding use of internal and external dependencies, and I wish I'd built it earlier in my career so I could've had it for other companies I've worked at!
-
Keeping up with EOS and EOL hardware and software
This is neat: https://endoflife.date/
-
Looking for a 3rd party library of EOL/EOS software support dates
I'm looking for a 3rd party vendor that can do the mindlessly tedious work of maintaining a library of software support dates. Think hundreds of thousands/millions of versions of software in an enterprise with ridiculous tech debt. Something like endoflife.date but much more far encompassing.
What are some alternatives?
pocketbase - Open Source realtime backend in 1 file
WordOps - Install and manage a high performance WordPress stack with a few keystrokes
redwood - The App Framework for Startups
django-DefectDojo - DevSecOps, ASPM, Vulnerability Management. All on one platform.
wasp - The fastest way to develop full-stack web apps with React & Node.js.
xeol - A scanner for end-of-life (EOL) software and dependencies in container images, filesystems, and SBOMs
turbo - The speed of a single-page web application without having to write any JavaScript
radiofeed-app - Simple podcast aggregator
Sharetribe - Sharetribe Go is Sharetribe's old source-available marketplace software, which was also available as a hosted SaaS product. Sharetribe Go is no longer actively maintained.
public-iperf3-servers - A list of public iPerf3 servers...
readability - A standalone version of the readability lib
digraph - Organize the world