Michael Nordmeyer

I have implemented this and added couple more tests for secret handling. It always works in vhosts mode, even if there's just one hostname. It errors out on launch if...

Sorry for not getting back the last couple of weeks. My current solution runs for a month on my server without problems: https://github.com/michaelnordmeyer/agate/tree/272-separate-meta-presets-for-virtual-hosts

Yes, I mentioned this and even wrote some code to at least log this. It's not a nice situation to be in. What's missing from your rationale is that currently...

Any update?

I meant that there's no artifact linked on the [GitHub release page](https://github.com/jekyll/jekyll/releases), which from my understanding means it wasn't released on GitHub, but only on rubygems.org.

You mean the confusion if someone wonders why there's a newer version available than on the canonical website (= here)?

Project's or maintainer's accounts has been compromised before, but mostly only one and not all. I think it helps a lot if all the relevant site have the same version.

> ``` > if [ -f /usr/local/share/bash-completion/bash_completion ]; then > source /usr/local/share/bash-completion/bash_completion > fi > ``` The usage of `$(brew --prefix)` instead of `/usr/local` makes it even nicer. ``` if...

It is also not great, that a `.meta` file in `/content/example.com/subdir` can configure files in other directories. It should only be applicable to content in the directory it is located...

Citing from the docs to clarify: > You can also enable a central configuration file with the -C flag (or the long version --central-conf). In this case Agate will always...