I built hoist, a small push-to-deploy tool for one Linux box (systemd + Cloudflare Tunnel, Python stdlib). To keep myself honest I installed Dokploy on the same laptop and deployed the same Dockerfile app through both, polling the public URL every 50 ms:

• push to live, median of 6: 1.54 s vs 2.53 s
• downtime during swap: 0.00 s vs ~0.1 s
• broken build: old version keeps serving on both

The first run, hoist lost (0.65 to 1.45 s gap during rollover). The fix was a small TCP front that owns the public port and only switches once the new container answers HTTP. Method, raw logs and bugs found are in docs/benchmark.md.

One laptop, one competitor: a method, not a verdict. I'd like critique on the method more than the tool.

Built with AI assistance (Claude), designed and tested by me.

https://github.com/nikhilcherry/hoist

Im planning on buying a webdomain soon to run a few projects and i just want to make sure i am able to do it i am planning on buying with ventraip since i can verify with my medicare card. just want a second opionion

I've been using WPBakery for years and have bought 21 "lifetime" licenses over time. I regret every single one of them at this point.

The update process is a fucking nightmare. It's been bad for years. As a "lifetime" licensed user you can't just update from the WP dashboard if you don't have a support license. I don't need support. I just need to update the plugin. But to do that simple task, you have to log in to the WPBakery site, find your version/license and then download a ZIP. This ZIP has to be unpacked and transferred to your site. And ofcourse the site breaks for a few seconds in the process

How can this be right? In Denmark we have this saying: "May your ass itch and your arms be too short to scratch it." – The late stage capitalist scumbag at WPBakery that came up with this should have the biggest itch and the smallest arms IMO.

I've been using WPBakery for years and have bought 21 "lifetime" licenses over time. I regret every single one of them at this point.

The update process is a fucking nightmare. It's been bad for years. As a "lifetime" licensed user you can't just update from the WP dashboard if you don't have a support license. I don't need support. I just need to update the plugin. But to do that simple task, you have to log in to the WPBakery site, find your version/license and then download a ZIP. This ZIP has to be unpacked and transferred to your site. And ofcourse the site breaks for a few seconds in the process

How can this be right? In Denmark we have this saying: "May your ass itch and your arms be too short to scratch it." – The late stage capitalist scumbag at WPBakery that came up with this should have the biggest itch and the smallest arms IMO.

Mi hermano ganó (su proyecto fue aprobado) en toy no toy en su última edición que transmitieron por telémetro y Mayer le ofreció $15k para invertir en su proyecto, hasta el día de hoy todo fue un teatro y nunca hicieron nada en apoyar, taquillaron todo eso y no apoyaron los emprendimientos, no solo fue mi hermano, ninguno de los otros participantes se llevó nada, toda una estafa en la que lucraron con eso, con la imagen de los participantes y se llevaron toda la plata de los patrocinios de empresas grandes que participaron.

Que burla, alguno más tiene información?

Hi everyone!
I’d really appreciate some advice from people with experience building corporate websites with WordPress.
I recently joined a company in a digital marketing role, and the company is currently going through a rebranding process. I’ve been given the opportunity to take ownership of the new corporate website, and I’ve already created the design myself.
Now I want to move on to the development and implementation phase using WordPress.
I have some previous experience with WordPress. I’ve built a few websites and worked with themes and plugins, but I’ve never developed a website for a company of this size or within a corporate environment.
I’m considering using WordPress Studio together with Claude (Claude Code) to help me build the website and potentially develop a custom theme. However, I’m not sure whether this is a good approach or whether I might end up overcomplicating things, especially when it comes to long-term maintenance and handing the project over to an external agency.
Here are some things I’d particularly appreciate your advice on:
Would you recommend starting with an existing theme (Astra, GeneratePress, etc.), using a Full Site Editing/block theme, or building a completely custom theme with Claude Code?
Is using Claude Code to develop a custom WordPress theme a good idea for this type of project, or could it introduce unnecessary complexity?
Would WordPress Studio be a good development environment, especially if I want to work with a cloud-based workflow?
How can I make sure the website is properly structured and easy for an external agency to take over and maintain?
What should I consider from the beginning regarding reusable blocks, plugins, SEO, performance, responsiveness and compatibility?
What would be the best workflow for development, staging and production?
My intention is to handle the design implementation, website structure, content, reusable blocks and on-page SEO. Later on, an external agency will most likely take over the more advanced technical aspects, such as security, hosting infrastructure, maintenance and further optimisations.
I want to make sure I build something professional, scalable and easy to maintain, rather than creating technical debt that someone else will have to deal with later.
There is also a personal motivation behind this project. I’m still relatively new to the company, and my current salary is quite modest. I see this as an opportunity to demonstrate my skills, take on more responsibility and deliver something tangible that I can use to support a salary review at the beginning of next year.
If you’ve worked on similar corporate WordPress projects, especially using AI coding tools such as Claude Code, I’d love to hear about your experience.
Would you use Claude Code for this project? Would you build everything from scratch or take a more conventional approach?
Any recommendations, resources or lessons learned would be greatly appreciated.
Thanks in advance!

On a subdomain Multisite install, WordPress by default scopes its auth cookies to the network domain: ms_cookie_constants() sets COOKIE_DOMAIN to '.' plus the network's cookie_domain if one is set, otherwise the network domain. (ms_cookie_constants reference)

Why it matters: say old-staging.example.com was CNAMEd to a host or page builder, the account was closed, and the DNS record stayed. If that provider lets anyone claim an unclaimed hostname, someone else can serve content on your subdomain (OWASP calls this subdomain takeover).

The record itself leaks nothing. The risk is that when a logged-in admin's browser makes a request to that subdomain, it sends any cookie whose Domain, Path and Secure attributes match, including wordpresslogged_in*, to the server the other person now controls. (MDN on Set-Cookie)

To find candidates, start from your DNS zone. One useful cross-check is certificate transparency logs (crt.sh, query %.example.com), which often surface old hostnames that got their own certs. They won't list names covered only by a wildcard cert, so treat them as a supplement. Then for each name:

dig +short CNAME old-staging.example.com dig old-staging.example.com # NXDOMAIN vs NOERROR curl -sI https://old-staging.example.com

A CNAME whose target returns NXDOMAIN is the classic red flag. A provider's generic "no such site" page only matters if that provider actually lets a stranger claim the name, so check their docs.

When you decommission, remove the DNS record first, then delete the environment or cancel the service. The other order leaves a window where the name points at something nobody owns.

For those running subdomain networks or sharing COOKIE_DOMAIN: do you audit the zone when a site leaves the network, or does DNS just accumulate forever?

Earlier this year before I knew client-side image processing was coming to WordPress 7.1, I created a free and open source WordPress plugin called Menagerie. It originally converted any image upload to AVIF or WebP in the browser, then uploaded saving some server bandwidth. So, pretty much what WordPress core can do now. This is always painful when you make a plugin and months later it's in core. Oh well.

Not all is lost though! Menagerie is still very useful. I stripped out what Core now does and left/enhanced the parts that Core doesn't automatically do. Core doesn't automatically ensure every upload converts to AVIF or WebP. Menagerie steps in to make sure that happens, gives you a JPEG fallback image, ensures your images are wrapped in <picture>, and provides a bulk image converter for your existing images. Plus, has a nice little toast message to confirm if the conversion was successful or not.

Tools within Performance Lab are another option. But, those are all server side I believe? And, a lot... Look at all those plugins that the Performance Lab page lists. Is all of that necessary? Depends on the situation and who you ask I suppose.

TL;DR

• Not Menagerie: WordPress 7.1+ processes your images in the browser when possible and then uploads
• Menagerie forces AVIF or WebP conversions; Still WordPress 7.1+ doing it in the browser when possible, but Menagerie is telling it to go with AVIF or WebP based on settings
• Menagerie creates your JPEG fallback for when a WebP or AVIF image can't be displayed
• Menagerie wraps images where possible in <picture>
• Menagerie gives you Open Graph image settings
• Menagerie lets you quickly convert all existing images

See also: https://wilcosky.com/my-quest-for-image-sanity/

The form is a small thin strip 3 text lines in height tops. I'm struggling to find the best placement for it where it doesn't disrupt from the customers journey.

I had considered placing it at the top of all product pages but then felt since those are my landing pages from paid ads that's probably a poor choice because that page is at the customers buying decision point. I had considered very bottom of all pages but felt that might be too hidden as well...

I had also considered the top of collection pages but felt that might distract visitors exploring. Where can you place this where it feels appropriate in the customers journey and doesn't feel spammy to the customer?

I build a Gym Management System with QR Code scanning for check-in with points system. I did use crocoblock Jetengine & JetFormBuilder. Right now it is working and I will use it next week. What do you think of building web app using wordpress?

Small site on shared hosting, LiteSpeed Cache plugin with QUIC.cloud as the CDN (DNS on QUIC.cloud too).

Right now I hit "Purge All" after every content or theme change, otherwise visitors sometimes get the old version. It works, but it feels like a sledgehammer.

For those running LSCache + QUIC.cloud:

- Do you rely on the auto-purge rules, or purge manually?

- Any settings you changed that stopped stale pages from showing up?

Not having a problem exactly, just want to set it up the right way before the site grows.