So Mercurial lost its biggest hosting platform. Sad to see it because I always thought that it has much more usable CLI and much better branching system for corporate development than git.
After much consideration, we've decided to remove Mercurial support from Bitbucket Cloud and its API. Mercurial features and repositories will be officially removed from Bitbucket and its API on June 1, 2020.
My new library to allow composer to read config from YAML file. There is some demand in comments for composer config but the developers are not interested and most 3rd party attempts to solve it are limited to yaml2json converters.
I tried a slightly different approach. There is a command in the composer itself that changes the way the config is read:
composer global. During its execution it changes current working directory, resets composer state, and forces the composer to read config from another directory.
What I tried to do: I put yaml2json converter in place of
global's directory changing code, and it seems it worked. Of course, some things got broken like any command that tries to change composer.json will no longer have any effect, however many people don't use them and it may be an acceptable tradeoff for using yml-based config.
You can find the project on my new dev website: https://sandfox.dev/php/composer-yaml.html
Interestingly, it's also the end of urpmi with both Mageia and OpenMandriva switching to dnf.
It seems rpm world entered a semi-unified state with dnf and zypper, both libsolv based and partly interoperable
I never expected this blog to go political but the situation became outrageous
Just ported the blog to Pelican and removed all Jekyll files. Currently it seems the most logical choice for me
First, I started to use reST much more extensively than Markdown and I want a blog generator that supports it better
Second is my new interest in Python
Third, Pelican seems to have much more features that I like compared to Jekyll and other static generators that I tested, especially Python ones (however Nikola also seems a good alternative but I had to stop at something)
Yesterday I moved two of my ruby gems, journald-native and journald-logger, to
theforemanGitHub namepace. Developing them further is out of my current professional interest and hopefully the Foreman project will be a good home for them.
It's hard to say farewell however to the most popular library I created so far :D (8 GitHub stars, 57000 downloads)
I've found no such projects so I had to write my own. Here it is: sandfoxme/phpstorm-metadata-export. It currently supports exporting data from Pimple and has 3 integration middlewares: for Slim, for Silex and for Psr-15 compatible frameworks.
P.S. Code completion support for ArrayAccess containers seem to be currently broken in PhpStorm (WI-33309, WI-35503). So I don't currently recommend replacing Silex Idea Plugin with this library unless you use Pimple in Psr-11 compliant way (like Slim does by default)