moe

Any reason this is not getting merged? On postgres the error looks like this: PG::Error: ERROR: relation "migrations_name_index" already exists: CREATE INDEX "migrations_name_index" ON "migrations" ("name")

Possibly it's postgres specific? I couldn't find a way to make my above snippet resilient - it always breaks when the server is restarted.

Quick tip in case you want to upgrade the main server; Hetzner offers 32G / 2x4T Servers for ~70 CAD: https://www.hetzner.de/dedicated-rootserver

> might cause memory issues as each build process uses quite a lot of memory > Hence you might want different defaults for --jobs and --parallel-fetch Agree. If both get...

Possible alternative/related: * Write all available options into the generated `shard.yml` (atm at least `crystal: ` is missing, possibly others) * Unify `shards init` and `crystal init`? Might be just...

As an idea for a migration path: How about retaining the current behaviour when the specified version is < 2.0 but make `shards` raise a syntax error when it is...

+1 for frontmatter. For me it's also the single reason why I can't use harp.

Hm, fwiw, I'm using Docker on a M1 Mac (but as seen above, docker runs in amd64 emulation, so I think in _theory_ it shouldn't make a difference). Can consistently...

Someone on a *M1* Mac I should add. (but thanks nonetheless! 🙂) Some new findings (also updated the description above accordingly): * It's actually **not** related to `--static` at all....

@straight-shoota > Using the working 1.1.1 image, you could build a dev version of the compiler After some more dabbling I'm afraid that may not provide further insight. For curiosity...