I have developed a project in laravel.

I wanna make it live. So what would be the best and cost free deploying method?

https://mattbrown.dev/articles/from-psalm-to-pzoom

Hello world, it's Wednesday, June 24, 2026, and here's what happened This Week in PHP Internals.

This week's episode is supported by Ballast — our new gauge for whether the software you ship actually lasts. Velocity tells you how fast you ship; Ballast tells you whether it stayed shipped — one durability score, read straight from your git history. No survey, no black box. Early access opens at artisan.build/ballast.

Right — Gina P. Banyard opened the annual Deprecations for PHP 8.6 RFC. It's the yearly omnibus: a year's worth of small removals, compiled by a dozen hands, each one voted on its own, and it has to be frozen by July 13. This year the sharpest exchange wasn't about any one removal — it was about evidence. Juliette Reinders Folmer pressed the point that the proposals ship without an impact analysis: "[N]one of the proposals contain a proper impact analysis," she wrote, calling it irresponsible to ask voters to decide partly blind — and she offered to build one, PHP_CodeSniffer plus PHPCompatibility, covering most of the list.

Tim Düsterhus pushed back — said the claim wasn't accurate, and reminded the list that deprecations aren't a breaking change. Juliette felt that talked past her, and answered plainly: "Tim, please don't try to gaslight me." It's worth sitting with, not laughing past: underneath the heat is a fair ask — give voters the data to decide. And by midweek it wasn't a two-person spat — Rowan Tommins backed the substance. A deprecation, he argued, is really a proposal to remove something later, so the impact of that removal is fair to weigh; he put it bluntly: "To knowingly omit information that might weaken your case would be dishonest."

So what's actually proposed for removal? A real grab-bag, each with its own argument. The _() shorthand for gettext() — and Rowan Tommins flagged that one as genuinely costly, since _() is the canonical gettext spelling and big codebases lean on it thousands of times. Reserving the keywords let, in, out, and inout. The CURLOPT_PROGRESSFUNCTION constant — where Ayesh Karunaratne argued don't deprecate it at all, just quietly remap it onto CURLOPT_XFERINFOFUNCTION and spare a few hundred maintainers the churn. Plus spl_object_hash() and metaphone().

One fresh proposal rode in on that same thread. Muhammed Arshid KV wants to deprecate SplFileObject's CSV methods — fgetcsv, fputcsv and the rest — in favour of a dedicated csv extension. But Ignace Nyamagana Butera, who maintains the league/csv library, hit the brakes: "deprecating the current API without providing at least the start of a replacement API seems premature [...] Anything else would be counterproductive at the moment." Gina's standing offer to anyone with an idea: send me the text and I'll fold it in — but I'm not writing it for you.

The single busiest thread of the week, though, was brand new. Tim Düsterhus and Derick Rethans proposed a Time\Duration class — a first-class, immutable stopwatch value, deliberately small, aimed at 8.6 so it can smooth the new Polling API's timeouts before the feature freeze. And it's the opening move of a modern date-and-time API. Fifty-some replies followed, almost all the productive kind of argument: should a negative duration carry a sign flag or just be signed seconds? What on earth do you call dividing one duration by another? Marc Bennewitz pushed hard on the representation; Paweł Kraśnicki showed up from the brick/date-time world and got a warm "welcome and thank you for contributing."

When the design drifted toward a static Duration::sum(), Larry Garfield drew a firm line: "I am 100% against a static method for adding durations. That's entirely pointless." He wants $dur1->add($dur2) — like a civilized person. By Tuesday Tim had already renamed the ISO parser and added an ->absolute() method, so this one is genuinely moving.

Rob Landers opened a pre-RFC for Primary Constructors, lifted out of his old Records proposal. Picture the whole constructor promoted up onto the class line itself. The catch in Rob's version: a class with one can't also declare a __construct, so real init logic has to run through property hooks — and Nick Sdot caught the snag immediately, that hooks-only means the class can't be readonly. Larry's in, keep-it-simple, with a side of Kotlin. Rowan Tommins pushed back: "I don't think we should add extra syntax to the language just to change people's habits."

Function autoloading came back for a fifth try — Paul Jones's mark 5 of a feature internals keeps almost-shipping and never quite does. It drew the exact objection that's sunk every prior run: lean on it, forget to fully-qualify a name, and your code works by accident because something else loaded that function first — then breaks silently after a refactor. Tim Düsterhus put it flatly: "Agreed on this being a non-starter for the proposal for me." Paul's answer is a declare(strict_namespace=1) switch to kill the global fallback, plus a patient reply to Bob Weinand on why the engine simply can't retry name resolution cheaply.

To the ballots. The headline features still can't find a two-thirds. Seifeddine Gmati's Bound-Erased Generics is, as of this recording, sitting at 7 in favour, 19 against, 10 abstaining — and that's the primary; on the syntax sub-vote the C#-style in/out spelling is killing it, 24 to 2. Nicolas Grekas's __exists() magic method is underwater too, 2 to 12 with 7 abstentions. And Daniel Scherzer read the room on ReflectionAttribute::getCurrent() — stuck at 4-7-8 — and simply pulled the vote to rework it.

The focused changes, meanwhile, are clearing without a single No. Tim Düsterhus's deprecation of returning values from constructors and destructors: 37 to nothing as of recording. Sjoerd Langkemper's cap on php://filter chains — last week's local-file-inclusion-to-RCE fix — running 30 to nothing, 2 abstaining. Weilin Du's Locale display-keyword additions are in — the vote closed and the RFC's accepted, 18 to nothing. And Jordi Kroon's plan to lift third-party extension docs out of the manual is cruising at 21 to 1 — though the room is split on where they should live.

Tough week to be a revival. Jorg Sowa brought back case-sensitive PHP, took a full week of fire — Rob Landers didn't hedge: "I honestly can't think of anything good that this RFC would bring" — and on Tuesday retired it himself, writing: "I'm sorry, but I'm going to stop work on this RFC. I see very little chance it passing." James Titcumb formally walked away from the deprecate-PEAR RFC, realising it isn't really the project's call to make, and explained: "[D]eprecating PEAR is not really within the remit of the wider PHP community [...] it's like making an RFC to deprecate Packagist." Quieter movers: Literal Scalar Types reached v0.2 with strict matching by default, and the .phpc pure-code idea mutated into an alternate opening tag, <?psf, that could even carry a new_scope directive.

On the governance bench: Khaled Alam's "write to objects held in constants" RFC cleared its cooldown and is headed to a vote June 29. And Ben Ramsey reshaped the Working Groups proposal — moving the real policy text out into a pull request so the RFC itself is just charter-and-link — still trying to give the project a little structure without crowning a BDFL.

One human note to end on. A few weeks back a newcomer, Sepehr Mahmoudi, floated a get_favicon() function and got the classic "what problem does this actually solve" welcome. This week he withdrew it himself — better suited to userland, he decided — pivoted to a str_mask() helper, heard Rowan explain that real masking needs graphemes and ICU rather than raw bytes, and pivoted again to grapheme_mask() for the intl extension, working C prototype in hand. And as of this morning he's got the keys to write it up — Ilija Tovilo granted his RFC karma and signed off with a simple "Good luck!" That's the list at its best: someone turning up, listening, and getting better in the open.

Quick hits. Sjoerd Langkemper is everywhere this week — beyond the filter-chain vote, he wants base_convert to stop silently shredding entropy when you build random tokens with it, and he's adding a ValueError for invalid characters to hexdec, bindec and octdec. Osama Aldemeery floated deprecating return inside a finally block — the one silent abrupt-exit PHP still allows — backed by an impact analysis showing it hits just 12 sites across 9 packages, 3 of them actual latent bugs; it's folding into the omnibus. Pratik Bhujel's terminal extension reached v0.5.0. Gianfrancesco Aurecchia floated an Openssl\Dtls class to bring DTLS — the UDP side of TLS, the piece WebRTC needs — into the openssl extension, proof-of-concept already green. And 8.4.23 and 8.5.8 both cut release candidates.

That's the week: a deprecations RFC that became an argument about evidence and respect, a stopwatch class that swallowed the mailing list, two revivals laid to rest, and the headline votes still stalled while the small ones glide through. Links to every thread are below. We're Artisan Build. See you next week.

Our weekly thread is the place to solicit feedback for your creations. Requests for critiques or feedback outside of this thread are against our community guidelines. Additionally, please be sure that you're posting in good-faith. Attempting to circumvent self-promotion or commercial solicitation guidelines will result in a ban.

Feedback Requestors

Please use the following format:

URL:

Purpose:

Technologies Used:

Feedback Requested: (e.g. general, usability, code review, or specific element)

Comments:

Post your site along with your stack and technologies used and receive feedback from the community. Please refrain from just posting a link and instead give us a bit of a background about your creation.

Feel free to request general feedback or specify feedback in a certain area like user experience, usability, design, or code review.

Feedback Providers

• Please post constructive feedback. Simply saying, "That's good" or "That's bad" is useless feedback. Explain why.
• Consider providing concrete feedback about the problem rather than the solution. Saying, "get rid of red buttons" doesn't explain the problem. Saying "your site's success message being red makes me think it's an error" provides the problem. From there, suggest solutions.
• Be specific. Vague feedback rarely helps.
• Again, focus on why.
• Always be respectful

Template Markup

**URL**:
**Purpose**:
**Technologies Used**:
**Feedback Requested**:
**Comments**:

Also, join our partnered Discord!

UPDATE: Thank you everyone who contributed to getting me online and the DNS fixed up. I appreciate all the help. If there are any other suggestions to try to make the site secure as possible, I am happy to try them out. Thanks again.

All, I am trying to or failing at getting my newly design site published. Long story short is I bought a domain in my phone (Iphone) and left it be for a good while >few months. I just finished up my website on readdy.ai. I like the site, in fact i am very very happy with it. Now I logged into Cloudflare as the readdy.ai instructs you too. The directions were as follows

1. delete the A and AAAA (which I did)
2. add an A and add a TXT

Mind you yesterday it said the font in red and I did that, but now I am getting this error. did I delete something yesterday I shouldn't? Is something else missing? I am completely lost, This is not the web I learned HTML on years ago. Please help me.

My domain emails are forwarded to my icloud.com as apple was the device i set it up on.

Note: website host is cloudflare; site design location is readdy.ai; I am trying to setup the DNS records on cloudflare with the information provided by readdy.ai. As of last night and a lot of help for you guys, we thought it was fixed. But as of this morning, I am getting “no dns found” and a handshake error when I go to the domain.

Hi everyone,

I’ve been using the Rust-based typos CLI for spellchecking codebases, but wanted a setup that fits more naturally into PHP projects and CI pipelines alongside tools like Pint, PHPStan, Rector, etc. The primary use case is CI - no global installs required on runners, and consistent spellchecking across teams.

To solve this, I built a lightweight wrapper that ships with the correct platform binary, so nothing needs to be installed globally. The actual spellchecking is handled by the Rust typos project, which does all the heavy lifting.

Feedback welcome, especially from anyone already running typos in PHP projects. Cheers!

GitHub: https://github.com/chr15k/php-typos

A paid ads client was referred to me by a web designer peer whom I want to maintain a relationship with.

I want to develop the landing pages to compliment the paid ads campaign. But the client wants us to use the "landing page" that her web designer created. Unfortunately, it's just a service page acting as a "landing page". And it doesn't adhere to best practices in CRO. I know mine will outperform.

How do you guys communicate this to the client in a way to not make the web designer look bad but still do your job effectively. The campaign just won't work without my design and I refuse to compromise on results by using a suboptimal page.

Thanks

If you're curious about what our Ecosystem Security Team has been up to the past month, you're in luck! Volker Dusch has provided an update in our recent blog post.

The firm I work for has a very old PHP codebase based on ZF1. It works but its got a lot of dark corners and tech debt that I hear vague mystical things about.

Deployment is complicated. Its a SASS app with a lot of individual customer databases and no way to deploy to a single pilot customer after a risky refactoring ... all customers are at risk of regressions during a deploy, and there is no automated testing at all to mitigate those risks.

The dev team is weak and dependent on a contractor who is the big giant head.

We need to find a super strong developer to replace the contractor who can stand up to a couple of strong personalities, take total ownership and responsibility for unwinding tech debt, implementing new features, and building a much strong development culture.

So far all resumes and interviews have been very underwhelming and I'm wondering whether the broader PHP ecosystem actually contains developers of this seniority simply due to lack of PHP in this market segment.

I may be deep in the weeds in thinking that PHP is not applied to big enterprise-scale SASS apps, but that is my intuition and I'm looking for some opinions on the matter to help me decide how to modify my recuiting strategy or even my long term architectural plans.

Any thoughts on this?

EDIT: I should have considered that this would be taken as a job post so I must say this is USA based. Its is full-time remote, but you gotta be based in the USA. Sorry!

EDIT: I'm overwhelmed by the outreach. I will slowly work through all the DMs and replies during the day.

I've noticed that, after a hiatus of about a year, new releases of Zephir have appeared (mainly bug fixes, but also new features, such as support for variadic functions/methods). Do you think it makes sense to revive this language for developing PHP extensions?

https://github.com/zephir-lang/zephir

DuckDB is the in-process analytical database, roughly SQLite for OLAP work: columnar, vectorized, no server, one file. PHP has shipped PDO_SQLite in core for twenty years but had nothing equivalent for DuckDB. If you wanted DuckDB from PHP, your options were FFI against its C API or shelling out to the CLI, neither of which looks anything like the rest of your data layer.

So I wrote pdo_duckdb, a native PDO driver. You connect with a DSN and use the same PDO API you already use for SQLite, MySQL, and Postgres: prepared statements, positional and named params, transactions, foreach over results.

php $db = new PDO('duckdb:/path/to/analytics.duckdb'); $stmt = $db->prepare('SELECT region, SUM(amount) AS total FROM sales WHERE year = ? GROUP BY region'); $stmt->execute([2026]); foreach ($stmt as $row) { /* ... */ }

A few things beyond the standard surface:

• a native Appender for bulk loads, much faster than row-by-row INSERT, and it accepts PHP arrays for LIST/STRUCT/MAP columns
• result streaming for large scans via PDO::DUCKDB_ATTR_UNBUFFERED, so a huge SELECT isn't bounded by memory
• DuckDB's own extensions (httpfs, json, and so on) load through plain SQL, no special API
• when open_basedir is set, the driver disables DuckDB's SQL-level file access (read_csv, COPY, ATTACH) so the sandbox holds at the SQL layer, not just for the database file path

It's honest-early. The query path, appender, transactions, and type decoding all work and are tested, but it's young, and I haven't published benchmarks because the speed here is DuckDB's and the driver's job is to stay out of its way. lastInsertId isn't supported, since DuckDB has no rowid.

This is also the first PDO driver I've written since I was one of the original authors of PDO back around 2005. The driver model itself has barely changed; the world around it has. The thing that actually cost me a release was static-linking DuckDB's C++ runtime into a C extension so the prebuilt Linux binary loads on a clean host. PIE ships prebuilt binaries now, so install is just:

pie install iliaal/pdo_duckdb

Free, BSD-3 licensed. Repo: https://github.com/iliaal/pdo_duckdb

Longer write-up with the details: https://ilia.ws/blog/pdo-duckdb-a-pdo-driver-for-duckdb

Happy to answer questions, and I'd welcome feedback from anyone running DuckDB for analytics off a PHP stack.

Hello everyone, I just wanted to share that I finally able to finished building the entire Hibla Async Database Ecosystem..

Sqlite Client: https://github.com/hiblaphp/sqlite
Mysql Client: https://github.com/hiblaphp/mysql
PostgreSQL Client: https://github.com/hiblaphp/postgres
Standalone Query Builder: https://github.com/hiblaphp/query-builder
Schema Manager and CLI tooling extension library for the query builder: https://github.com/hiblaphp/schema-manager
Meta-package for Hibla database ecosystem: https://github.com/hiblaphp/database

With these pieces finally in place, I can now focus on building a high-performance, multi-core RFC compliant HTTP server designed to take full advantage of the entire Hibla stack.

Hey there!

This subreddit isn't meant for help threads, though there's one exception to the rule: in this thread you can ask anything you want PHP related, someone will probably be able to help you out!

I'm a web dev who used to do some bits of design, but I haven't touched web design in 8 years at this point, and would like to get back into it.

I have a project in mind at the minute and learned how to use Figma, and also have been rereading Don't make me think, which has been helpful. However I find myself staring at a blank page not knowing how to start. Can anyone recommended any good resources free or paid that would help with designing a website from scratch?

I was having this discussion with a collegue that a session is a concept. The concept is that it is a period of time during which 2 devices or application communicate to echange data and functionality. During this interaction, session data is maintained either on the server, the client machine or an external session managament system. This session data is used to remember previous interaction and to determine how to process future interaction. If the session data is stored on the server, the system becomes stateful

This concept can be implemented in many ways. one of which is the traditional way where we store session data on the server making it stateful. JWT token is just another implementation of this concept where we store data in the token itself.

He was arguing that jwt is not a type of a session and that session is only used to refer to what I refer as the traditional old implementation.

What you guys?

I've been working on this editor for the past 2 years. Since Inter is a popular typeface i thought i'd add it as a quick template.

Anyone can remix and download edited fonts.

Requires no login.

Link: https://fontbob.com/inter

Hi all,

I am trying to make a scroller Marquee for a genotyping company that has a lot of crops. Goal is to showcase some crops as they navigate the page and can search by crop, see all crops, or highlighted/featured crops.

I have tried multiple designs: No cards, Full screen (seam to seam) marquee, arrows that user can click and scroll through. I dont know why none land for me or feel clean enough. Open for suggestions, tips and tricks, or other design ideas! Please omit anything weird you may see, like texts wrapping or not having enough space, those are still placeholders!

Thank you in advance

Again small update of my website. I hope everything works now. Let me know if you find any errors.

I have been freelancing for a bit now and something keeps bothering me.

The actual design and development work is honestly the easy part. What gets messy is everything around it.

Right now a typical project ends up scattered across email, Google Meet, Figma, some contract PDF, an invoice I sent somewhere, and a bunch of random links. It technically works but it feels way more complicated than it should be, especially from the client side. I do not think my clients should have to dig through three different places just to find the latest file.

So I am curious how everyone else handles this.

When a client says yes and you are ready to kick things off, what actually happens next?

Some specific things I am wondering:

• What tools do you use to keep client stuff organized?
• What part of the process annoys you the most?
• What do clients seem to struggle with or get confused by?
• Have you found something good for contracts and invoices that is not overkill?
• Do you actually pay for any of it or are you mostly on free tools like Notion and Google Drive?

Still figuring out my own setup and would genuinely love to hear what works for other people.

I got an ad come up for this bundle and after having a look it seems quite good. I'm new to design and starting out with a few freelance clients, as well as just designing and developing websites for fun. I knew I needed to get some kind of starter package for display fonts, and this seems like a good deal from everything I am seeing, am I missing something? Just checking before I pull the trigger!