Found by the work on #211. Checked against next at ef828f7.
README Getting Started has you copy the example config to config.yml at the repository root and put a real signing key in it, and pixad looks for config.yml in its working directory. .gitignore leaves out config.yaml and config.dev.yml but not config.yml, so that file can be committed. .dockerignore does not leave it out either, so the next make docker in the same tree copies it, through COPY . ., into a build-stage layer.
Suggested plan: add config.yml to .gitignore next to config.yaml, and **/config.yml to .dockerignore next to the local config entries #211 adds. Check the .dockerignore side as #211 does: plant the file at the root and two directories deep, build a COPY . . image, list it, remove everything.
Model: opus-5-5
Found by the work on https://git.eeqj.de/sneak/pixa/issues/211. Checked against `next` at `ef828f7`.
README Getting Started has you copy the example config to `config.yml` at the repository root and put a real signing key in it, and `pixad` looks for `config.yml` in its working directory. `.gitignore` leaves out `config.yaml` and `config.dev.yml` but not `config.yml`, so that file can be committed. `.dockerignore` does not leave it out either, so the next `make docker` in the same tree copies it, through `COPY . .`, into a build-stage layer.
Suggested plan: add `config.yml` to `.gitignore` next to `config.yaml`, and `**/config.yml` to `.dockerignore` next to the local config entries https://git.eeqj.de/sneak/pixa/issues/211 adds. Check the `.dockerignore` side as https://git.eeqj.de/sneak/pixa/issues/211 does: plant the file at the root and two directories deep, build a `COPY . .` image, list it, remove everything.
Model: opus-5-5
Built in #217: .gitignore now ignores config.yml, and .dockerignore leaves it out in every directory and in any letter case.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/pixa/pulls/217: `.gitignore` now ignores `config.yml`, and `.dockerignore` leaves it out in every directory and in any letter case.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found by the work on #211. Checked against
nextatef828f7.README Getting Started has you copy the example config to
config.ymlat the repository root and put a real signing key in it, andpixadlooks forconfig.ymlin its working directory..gitignoreleaves outconfig.yamlandconfig.dev.ymlbut notconfig.yml, so that file can be committed..dockerignoredoes not leave it out either, so the nextmake dockerin the same tree copies it, throughCOPY . ., into a build-stage layer.Suggested plan: add
config.ymlto.gitignorenext toconfig.yaml, and**/config.ymlto.dockerignorenext to the local config entries #211 adds. Check the.dockerignoreside as #211 does: plant the file at the root and two directories deep, build aCOPY . .image, list it, remove everything.Model: opus-5-5
Built in #217:
.gitignorenow ignoresconfig.yml, and.dockerignoreleaves it out in every directory and in any letter case.Model: opus-5-5