#vinylcache — Public Fediverse posts

👩🏻‍💻 my so-called sudo life - day 497: Mastodon stampede edition 🐘​

Dear Fedi friends,

You may remember how last year I was dealing with self-DDoS attacks every time I shared a link to my Wordpress or Ghost sites. Well, I solved the issue with Ghost (#VinylCache is brilliant) but I never found a solution for my Wordpress site... not even with #BunnyCDN. I guess I wasn't tweaking the right settings.

This is a pity because TBH the ActivityPub for Wordpress plugin is SO COOL and works flawlessly. I had to move my blog posts to Ghost and keep Wordpress as a static portfolio site. That being said, I never dared share links to my Wordpress site anymore because I would get about 4000 requests within 60 seconds and everything would freeze.

I just looked into #BunnyCDN's settings again and tried to tweak them. So please bear with me for an experiment, sharing an old blog post and seeing what happens.

Wish me luck!

From the archives:

https://elenarossini.com/2025/01/my-so-called-sudo-life-time-matters/

#BuyEuropean #CDN #DDOS #MastodonHugofDeath #MastodonStampede #Wordpress #blog #MySoCalledSudoLife

New tutorial: Configuring TLS with haproxy

We show a low-maintenance, “configure and forget” solution for using TLS for client- and backend traffic with Vinyl Cache and haproxy.

https://vinyl-cache.org/tutorials/tls_haproxy.html

#vinylcache #haproxy #tls

My very rough test shows that Rust hyper can achieve ~119k requests per second, but vinyl cache formerly known as Varnish with 1s cache on front of a same URL can reach 96k requests per second.

https://github.com/Ciantic/stress-test-vinyl-cache/tree/main

#Rust #VinylCache #Varnish

WikiApiary is back online after having been down and overloaded for a long time.

Bawolff brought it back and did a ton of full stack performance work to optimise the whole system. Adding HTTP caching, tuning InnoDB, and more!

https://blog.bawolff.net/2026/03/giving-wikiapiary-kick.html

#MediaWiki #WikiApiary #Wikibase #Wikidata #VinylCache #VarnishCache #MariaDB #MySQL #webperf #SRE

Hmmm,

My impression was that #Varnish Software would be based off on the #VinylCache upstream.

But now it seems like they have effectively created a new "varnish" repository where they intend to follow upstream, with their own patches *and* features vinyl doesn't want?

I already see changed not upstreamed, and they seem to be pushing for existing varnish packages to point to the "new" upstream?

Why did #varnishcache change it's name to #vinylcache ?

Vinyl Cache, the FOSS project formerly known as Varnish Cache, has a new logo:

https://vinyl-cache.org/

#Vinylcache #Varnishcache

#vinylcache has left *) #github for self hosted #forgejo yesterday.

https://vinyl-cache.org/organization/moving.html

There is a also a bit about some additional measures we implemented and a mini-retro with mistakes made.

*) repos are archived to help people find the new location, and some related projects are still TODO

#varnishcache

#vinylcache forge migration in progress…

#varnishcache

More details on the #vinylcache move here: https://vinyl-cache.org/organization/moving.html

TL;DR: Expect github repos to soon be archived, get an account on code.vinyl-cache.org

#varnishcache

If you are a #vinylCache user, please prepare for the upcoming move to a self hosted #forgejo instance and register an account:

https://code.vinyl-cache.org/user/sign_up?jwt=eyJhbGciOiJSUzI1NiIsImtpZCI6IkRWZFVKUFU5QlJVVUNRdHl5Uk1xcS00TmdIVXZJVmtSbE5BUE5jeDgyMmciLCJ0eXAiOiJKV1QifQ.eyJhdWQiOiIvdXNlci9zaWduX3VwIiwiZXhwIjoxNzcxNDQwNjkyLCJpYXQiOjE3NzA4MzU4OTIsImlzcyI6Ii91c2VyL3NldHRpbmdzL2ludml0YXRpb25zIiwibmJmIjoxNzcwODM1ODkyLCJzdWIiOiJzbGluayJ9.LFDvydBh_cxhyvP1sOdobInlEr4OtqISQtwoDiYE6AvvI6q4A2PxqikFOrwpg5NP5dqSU84ctwxMmiDI61-ypk2nRGya6RW5xAu4PskcaDO8_41gob9SQ-MUtbJCBeldHpDJIrYi1GS_tmdjh4x2jEXne9vSoTXBAmFmh8k7c1gyJvtRJx_HJApPTbcreZ-ug2RjLGvK8zLf-llnPA1AeaeF1SRLZIGD6i8-wvT25u6Taaz64gPICl-I5k8mvwODCt1aZy3R9sUB9jY1YKxvKiBEhCpLn51Nr2cmSc9MzCOonqwsnIZ3Ql-aJo5BwAdvDl82fBiKOoZV6La7GOoW5Q

This link expires 2026-02-18T19:51:32+01:00.

After this date, anyone who already has an account should be able to help out,
unless we still get abused by spammers and need to close registrations again.

#varnishcache

"the team and I would like to thank you for your very efficient and thorough work supporting us" -- new client

When you work with clients long-term, it's natural for some things to become routine. That's why feedback like this is so meaningful and energizing.

Thank you, new client.

#varnishcache #vinylcache

Last call! Logo #contest!

Since #Cloudflare was recently facing a global outage, it’s a good moment to make you aware of a logo contest organised by an #opensource alternative #VinylCache.

Vinyl Cache, previously known under the name #VarnishCache, is rebranding itself and looking for a new logo and mascot. If you are a designer and would like to shape their visual branding, feel free to submit your sketches (no final designs needed) until the end of Nov https://varnish-cache.org/index.html#logo-contest

Announcing VCOT: OpenTelemetry Instrumentation for #vinylcache

We’re happy to announce to have opened the repository of VCOT (VinylCacheOpenTelemetry), a brand new open-source Go utility designed to enhance observability in Vinyl-Cache (and, for the time being, #varnishcache) environments through an integration with #opentelemetry.

VCOT parses Varnish Shared Logs (VSL) in real-time and exports telemetry data to OpenTelemetry-compatible backends.

https://gitlab.com/uplex/varnish/VinylCacheOpenTelemetry

a databricks report on smart load balancing in k8s makes the rounds.
i would like to mention that we solved this and other problems using the shard director in #vinylcache (formerly #varnishcache) years ago. for k8s we have viking (repo needs renaming).

and yes, l4 loadbalancing of http is, in most cases, the worst choice

http://vinyl-cache.org/docs/trunk/reference/vmod_directors.html#directors-shard
https://gitlab.com/uplex/varnish/k8s-ingress

Varnish Cache project to change its name to Vinyl Cache with after the next release (after today's 8.0.0, in March), per @bsdphk:

We have tried to negotiate with Varnish Software for many months about this issue, but their IP-Lawyers still insist that Varnish Software owns the Varnish Cache name, and at most we have being offered a strictly limited, subject to their veto, permission for the FOSS project to use the “Varnish Cache” name.

We cannot live with that: We are independent FOSS project with our own name.

So we will change the name of the project.

The new association and the new project will be named “The Vinyl Cache Project”, and this release 8.0.0, will be the last under the “Varnish Cache” name. The next release, in March will be under the new name, and will include compatibility scripts, to make the transition as smooth as possible for everybody.

https://fosstodon.org/@bsdphk/115208900512511929

#VarnishCache #VinylCache