WordOps VS endoflife.date

https://wordops.net is also nice to automate parts, if you don't mind that it's all running under the same user.

A simple efficient CLI stack that works well is WordOps.

Also, WordOps

Si te lo queres hostear vos: https://wordops.net/

I also just wanna give a shout out to WordOps, super simple to use, free and open source. Deploying a website with redis or fastcgi caching and SSL takes just a few seconds. Great support community too.

There's a brotli setting on CF that ignores your nginx's settings in speed -> optimizations -> brotoli (needs to have white on green checkmark). But for nginx's settings itself, I have this file as /etc/nginx/conf.d/brotli.conf assuming your /etc/nginx/nginx.conf has include /etc/nginx/conf.d/*.conf;.

You can put it on a $5-10 server on linode and upgrade to $20 server if you need to anytime. For an extra $5 it'll include daily backups, and one on demand backup. Last time I had to set it up it took me about an hour to get it running with a LEMP (Nginx, mariadb as a drop in replacement of mysql) stack from https://wordops.net/. But if you want it to stay htaccess compatible that a majority of wordpress plugins expect, should run with a litespeed stack.

If you're looking to cut costs I'd highly recommend checking out https://wordops.net/

I highly recommend using WordOps to manage the server. It makes setting up fast & secure Wordpress sites extremely easy.

> 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.

Here's the PR where it was added by a user, "Based on a Rails core team member's comment"...

A lot of the communications regarding End of Life for Support is done very effectively here: https://endoflife.date/

https://endoflife.date (not mine)

a little similar to endoflife.date if anyone has ever come across it for Software versions?

We do this at https://endoflife.date API, and it works quite well.

I've created the `db.json` with the [end of life](https://endoflife.date/) api.

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!

This is neat: https://endoflife.date/

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.