Been looking at Docksal this morning. It’s web dev tooling containers configured in code. First thoughts were: why duplicate all this work. However getting a zero config project running with a cross project cli utility is really nice. No more composer npm PHP* conflicts!
Category: Status
Some PHP tooling scripts require specific versions. I had compatibility issues running a code sniffer. PHP-version helped to set the default PHP interpreter.
Reorganise your todo list. It isn’t super productive but it gives you back control and understanding.
One does not simply install Wallabag. 👌
On how many devices can you watch Netflix? I’m at 10. 😓 Less is more, I’m failing.
These last few weeks has made me wary of committing further or ever developing for the Apple ecosystem; and working with OS projects ran by a major business.
Made a very simple to use TextPattern Docker setup where you provide your own TextPattern installation and database secrets then run docker-compose up github.com/svandragt/txpdocker
I guess we are fixing our rueful compatibility story by encasing our tools in fixed environments. We then write new tooling or containers when this is no longer usable.
That seems like a short term view of things.
We will end up with black box containers and needless layers of complexity.
Made a strategic change in Cuttlefish to make it as simple as possible, instead of as a test bed for tooling tech. So I removed Docker and PHPDox support.
Don’t bother with separate Main and Dev Firefox profiles, instead use Firefox and Firefox Developer Edition and sync them with an account each.