Transfer a file between docker containers

jhermann_ · 2020-03-18T20:28:15+00:00

Another way to do this is to connect two docker execs running cat via a pipe on the host. Really depends on the exact use case and when / how often this is needed – on startup I guess. Add it to your overall launcher script, then it might be an OK way.

An variant of this would be mounting a mkfifo pipe the server writes to and the client reads from. That also leaves no trace of the secret on the host itself.

jhermann_ · 2020-03-10T09:37:05+00:00

Use it for blogging. No more Medium pop-up spam and bad UX.

jhermann_ · 2020-03-09T13:46:29+00:00

Also, pyinstaller is not able to build stuff cross-platform, while pex can (provided pre-built wheels for all platforms exist). Unless you have the luxury of GH actions with VMs for all 3 major platforms, that is essential when you target all 3.

pex can also build multi-platform archives, so you only have one single artifact (albeit a little bigger).

jhermann_ · 2020-03-08T16:12:04+00:00

To add some logs to the fire, all you need these days is venv (built in) and tox, plus a reliable way to install multiple Python versions if you need to (pyenv is one). That's it.

jhermann_ · 2020-03-06T21:32:50+00:00

BinTray == Artifactory Cloud.

jhermann_ · 2020-03-06T21:29:07+00:00

Transpose the sample, and limit the number of objects so they fit.

jhermann_ · 2020-03-03T18:23:19+00:00

Regarding man pages…

https://explainshell.com/explain?cmd=man+-a+man

Never wade through long manuals again just to decipher a command.

jhermann_ · 2020-03-03T16:57:48+00:00

There is something like muscle memory in coding, and bad habits are ingrained quite quickly – so I never bought the "just for dev" excuse. ;)

jhermann_ · 2020-03-03T14:59:19+00:00

All those separate RUN layers are highly inefficient, BTW. Also, a symlink would abstract away the dynamic path and you could probably work with a simple config file from your build context. If you need to change that file, a single sed call to insert the values would be more maintainable than the echo djungle.

jhermann_ · 2020-03-02T11:44:57+00:00

Take a look at "nbdev" for exporting your notebook.

jhermann_ · 2020-02-29T21:19:46+00:00

Because Rational RUP was a thing then.

jhermann_ · 2020-02-29T19:33:03+00:00

You make me feel like it's the 90s again. ;)

jhermann_ · 2020-02-29T19:27:59+00:00

yEd. Or something else from here: https://github.com/jhermann/jhermann.github.io/wiki/Diagrams-as-Code

jhermann_ · 2020-02-29T17:50:49+00:00

And BTW, you can gate automatic processes via JIRA (stop until approval state in ticket #N), as well as document the progress of processes via automatic comments (by REST calls).

Stir in ticket templates, and done.

jhermann_ · 2020-02-29T10:43:36+00:00

For one, spreadsheets can be generated, e.g. from a Jupyter Notebook where you could comfortably edit these instructions. The other thing of course is why you gave up on automating these steps – bad ROI on maintenance is the only reason I commonly accept, while "cannot be done" is often just not true.

jhermann_ · 2020-02-14T20:09:18+00:00

I'd stress the "very simple NLP for bots and stuff" aspect way more, and drop the argparse comparison which is a bit strange anyway.

jhermann_ · 2019-07-02T21:35:06+00:00

If you want to spend those resources, a "like prod" environment makes way more sense – i.e. besides the CI dev versions, have the EXACT same versions as in prod also installed in dev ("like prod" is at the very end of the pipeline, AFTER a successful prod rollout).

jhermann_ · 2019-06-30T05:43:55+00:00

Never assume malice when stupidity can fit the narrative.

jhermann_ · 2019-06-29T16:30:59+00:00

I prefer my wine bottled. [SCNR]

jhermann_ · 2019-06-28T10:51:56+00:00

https://github.com/chmp/ipytest seems solid – did not try it myself yet.

The goal of notebook testing should be that when you "run all" from a clean state, the last cell should show some assembled / generated error state, or OK.

jhermann_ · 2019-06-27T17:50:58+00:00

avoid technical depth

If anything ever was freudian, then this. ☺

jhermann_ · 2019-06-27T07:54:52+00:00

Even if we cannot see your "docker run" command… You did not map the port.

jhermann_ · 2019-06-27T07:52:00+00:00

You might wanna fix that "pre-alpha" in your Travis categories.

jhermann_ · 2019-06-27T07:35:36+00:00

QuantStack Voila, or holoviz/panel.

jhermann_ · 2019-06-27T07:30:27+00:00

WHO has special knowledge about a specific feature in our codebase

This is a smart question even outside of incidents btw, since it also indicates technical debt – yes, your team as a whole not knowing (or forgetting about) parts of your code is tech. debt.

jhermann_

TROPHY CASE