getlaminas (@getlaminas@phpc.social)
Released: laminas/laminas-modulemanager 2.18.0
#php #laminas
https://github.com/laminas/laminas-modulemanager/releases/tag/2.18.0
Show Original Post
dima (@dima@dol.social)
I just realized I've spent over €500 on PHPStorm licenses since 2020.
What's funny is that the price kept creeping up slightly every year, even though JetBrains claims the renewal discount should make it cheaper over time.
After three continuous years of subscription, it's basically back to the same price I paid in 2020 for the first license.
…and on top of that, there’s the lovely 20% VAT I somehow still have to pay for reasons unknown.
#jetbrains #php #subscriptions #development
Show Original Post
dabiddo (@dabiddo@mstdn.io)
Rector Rules for Laravel - Laravel News
https://laravel-news.com/rector-rules-for-laravel?ref=dailydev
Show Original Post
scottkeckwarren (@scottkeckwarren@phpc.social)
One of my favorite new features added to #php85 is the ability to add the NoDiscard attribute to a function, so if we call a function without doing something with the return value, we'll receive a warning.
Learn about more of the new features at youtu.be/Wmsy2O_WysA
#phpc #php #webdesign #softwareenginnering
Show Original Post
getlaminas (@getlaminas@phpc.social)
Released: laminas/laminas-authentication 2.19.0
#php #laminas
https://github.com/laminas/laminas-authentication/releases/tag/2.19.0
Show Original Post
lo_fye (@lo_fye@mastodon.social)
Where should I look for remote jobs doing #php with or without #laravel?
I'm based in Canada, but my corporation can also invoice US companies and receive funds in US Dollars.
Show Original Post
lo_fye (@lo_fye@mastodon.social)
What #php or general #coding RSS feeds should I subscribe to?
Show Original Post
ingewikkeld (@ingewikkeld@phpc.social)
We are happy to announce that Ingewikkeld is joined by a new senior software engineer. Tom de Wit will be starting November 1st and will be doing #PHP software development and more. He has experience with (amongst other things) #Symfony and #Laravel. We are very happy with Tom joining us. Welcome Tom!
Are you in need of some help with your PHP project? Get in touch! Perhaps Tom could help!
Show Original Post
jclermont (@jclermont@phpc.social)
I like consistency. I talk about it a lot in these tips, because it lets me focus on the important decisions in my work. In today's video, I show an example with this when it comes to running composer scripts. #php #laravel https://masteringlaravel.io/daily/2025-10-17-video-be-consistent-with-composer-scripts-in-ci
Show Original Post
Dark_Chyper (@Dark_Chyper@pouet.chapril.org)
Helllloooooo youuuu !
Le tout premier de ma collection :)
#elephpant #elephant #php #karafun
Show Original Post
JosephLeedy (@JosephLeedy@phpc.social)
Integrating automated testing into my dev workflow has made a world of difference for me. Over the past couple of weeks, I was able to make a major architectural change to with the confidence that nothing was broken. I have an extensive suite of integration and functional tests that allow me to quickly verify that everything still functions correctly. Without this, I would have had to spend days doing manual testing and crossed my fingers that I didn’t miss anything.
Show Original Post
reynardsec (@reynardsec@infosec.exchange)
A grumpy ItSec guy walks through the office when he overhears an exchange of words.
devops0: I'll push the new image - just pull "latest"
ItSec (walking by): Careful. "latest" doesn't work the way you think.
devops1: How so?
ItSec: It's just a tag. Whoever pushes the image decides what "latest" points to. Sometimes it's the newest.
First, assume you have a local registry running on localhost:5000 and two Ubuntu images already present: ubuntu:23.04 and ubuntu:22.04. Tag and push both by their actual versions so the registry has explicit versioned tags. Then, on purpose, point latest to 22.04.
# start quick&dirty&unsecure local registry
docker run -d --name registry -p 5000:5000 --restart=always registry:2
# push explicit versions
docker tag ubuntu:23.04 localhost:5000/ubuntu:23.04
docker push localhost:5000/ubuntu:23.04
docker tag ubuntu:22.04 localhost:5000/ubuntu:22.04
docker push localhost:5000/ubuntu:22.04
# intentionally make "latest" refer to 22.04
docker tag ubuntu:22.04 localhost:5000/ubuntu:latest
docker push localhost:5000/ubuntu:latest
Now pull without a tag and see what you actually get. Omitting the tag defaults the client to requesting “:latest”. Because you explicitly set latest to 22.04, that’s exactly what will be pulled and run.
# pull without a tag -> defaults to :latest
docker pull localhost:5000/ubuntu
# verify the version by inspecting inside a container
docker run --rm localhost:5000/ubuntu cat /etc/os-release | grep VERSION=
VERSION="22.04.5 LTS (Jammy Jellyfish)"
If you now retag latest to 23.04 and push again, the same pull with no tag will start returning 23.04. Nothing "automatic" updated it; you changed it yourself by moving the tag.
That's the entire point, latest is a conventional, movable label, not a magical link to the newest software. It can be older than other tags in the same repository if someone set it that way. It can also be missing entirely.
For more grumpy stories visit:
1) https://infosec.exchange/@reynardsec/115093791930794699
2) https://infosec.exchange/@reynardsec/115048607028444198
3) https://infosec.exchange/@reynardsec/115014440095793678
4) https://infosec.exchange/@reynardsec/114912792051851956
5) https://infosec.exchange/@reynardsec/115133293060285123
6) https://infosec.exchange/@reynardsec/115178689445065785
7) https://infosec.exchange/@reynardsec/115253419819097049
#appsec #devops #programming #webdev #docker #containers #cybersecurity #infosec #cloud #sysadmin #sysops #java #php #javascript #node
Show Original Post