Liam Crilly
Liam Crilly
You read my mind! I am in favour of the tabs approach (with some state to remember which tab the reader prefers). Later we might have several API tools documented.
There is more than one ARM architecture. Let's be specific.
Also consider Docker `CMD` arguments so that a read-only filesystem can be used. See https://github.com/nginx/unit/issues/1144 A PID file is redundant, logs could go directly to /dev/stderr instead of a symlink...
The documentation refers to this simply as "control socket" https://unit.nginx.org/controlapi/#api-manipulation So I would also drop "API". Which also seems consistent with `unitctl --help` ``` $ unitctl --help | grep socket...
Given that we have the `type` and `version` as separate entities in the struct, it makes sense to have an array of objects instead of the simple naive array I...
I look forward to trying it :) I suggested an array of objects because we may find multiple versions of the same language module installed (especially for PHP and Python).
I actually meant something different but then realised that it's not possible to have ambiguous module names. So @ac000 's original example looks ideal.
Excellent! Well done @ac000
Presumably the global variable is not persisting across internal redirects (as was the intention)? Perhaps `js_var` is worth considering to avoid performing the newSession check twice?
Markdown requires special treatment IMHO, and should not be treated like source code or true markup languages. Primarily it needs to read well using GitHub's web view, but also be...