Simpler to keep everything in one compose file if you can, under a test
service that doesn’t build unless explicitly named
Un-weird that env var and use the normal, boring feature of defining environment
under your test
service
Simpler to keep everything in one compose file if you can, under a test
service that doesn’t build unless explicitly named
Un-weird that env var and use the normal, boring feature of defining environment
under your test
service
I’ve often been able to alias drun='docker compose run --rm --build'
and simplify down to:
drun test
Should be able to encode all those wayward args into docker-compose.yml
or Dockerfile
and only use vanilla docker commands – that’s the whole point of containerization
In the US? IMO only possible in exclusive environments similar to saunas at spas or membership-based clubs/gyms
There’s the practical distinction between “everyone can do it with some dedicated intent” (so few actually bother) vs “everyone can do it on a whim”
wanted to add something to the end of a for-loop, but had too little indentation
To address this, I prefer reducing length & depth of nested code, so the for
/while
is rarely ever not visible along with everything inside it. Others have success with editors that draw indentation lines.
opening up new/anonymous scopes
I occasionally use Python nested functions for this purpose
I find it’s possible to operate Python as a statically typed language if you wanted, though it takes some setup with external tooling. It wasn’t hard, but had to set up pyright, editor integration, configuration to type check strictly and along with tests, and CI.
I even find the type system to be far more powerful than how I remembered Java’s to be (though I’m not familiar with the newest Java versions).
I prefer that, though (it’s in my calendar, but I don’t have to accept). I really can’t stand Outlook’s email-based calendar workflow.
That’s only because the former already implies much of the latter, so they don’t need to repeat it
I’ve heard of publishing software to design photo albums/scrapbooks/cards etc. Is there a photo collection manager for archiving, sorting and filtering?
Given access to a large set of personal photos, say tens of thousands, it should be able to group, categorize, tag, and sort along a myriad of dimensions.
Example dimensions would be time, people and places. It would need some facial recognition/image classifier/similarity scoring capability.
There definitely are some cloud offerings today that do similar things, but I’d want it to work locally for privacy and practical reasons.
If talking about a closed source app, their whole goal is to move off of hosting closed source systems.
Article says the decision follows a successful pilot project, so they’re willing to absorb the short term costs. Optimistically in the long run, the symbiotic benefits of having a government entity using and supporting a full FOSS system will be huge.
Not surprising that PDF comments were being used as a task list/tracker. In the same manner, Google Docs supports “@-mentions”, “assign to”, and “resolved” functionality for comments.
All you can do is send feedback to Adobe somehow and hope they add that feature back in. In the meantime, best to find an alternative workflow.
I’ve created a Google spreadsheet to accomplish this sort of thing: Split Payment Calculator
It’s got formatting and locked areas to help layman usage, but it’s ofc still a spreadsheet UI and not a dedicated app. A bit of math proficiency and spreadsheet formula knowledge helps.
Could be replicated on other spreadsheet software like Excel or Calc, although Sheets solves a lot of problems at once, like accessibility, sync, versioning, sharing, etc
You can reference envs from the host in docker compose, so code it in instead of manually passing tribal knowledge in: https://stackoverflow.com/a/73826410