|
2 | 2 |
|
3 | 3 | - the `Justfile` commands are built so they would even work on a 100% fresh |
4 | 4 | setup, and will set up and initialize everything they need. |
| 5 | +- I removed `index: Index` from the context. There is no need to clone the |
| 6 | + crates.io index on a web- or build-server. The handful of places where we then |
| 7 | + still need the index just create the obj. |
| 8 | +- there was an error I had when calling `Index::peek_changes` from |
| 9 | + `crates-index-diff`. In there, we're using the github fastpath to check if |
| 10 | + there are new commits in the repo, without having to actually `git pull` from |
| 11 | + the remote. When I called `.peek_changes` in an async context, this lead to |
| 12 | + tokio errors because inside `crates-index-diff` we're using |
| 13 | + `reqwest::blocking`. Odd thing is: I couldn't find out why this doesn't fail |
| 14 | + on production. It might have started failing just after the config/context |
| 15 | + rewrite, which is not deployed yet. |
| 16 | + [#2937](https://github.com/rust-lang/docs.rs/pull/2937) |
5 | 17 |
|
6 | 18 | ## docker image |
7 | 19 |
|
8 | 20 | for now, these are production images, changing files will not auto-reload / |
9 | | -build the image. We could decide to do that layer. |
| 21 | +build the image. We could decide to do that layer. Also I don't want to copy the |
| 22 | +".git" folder into the image, just for the version number. I made the SHA a |
| 23 | +build-arg / env and used these in our codebase. |
| 24 | + |
| 25 | +The fallback to fetching the has from the repo still exists, we might be able to |
| 26 | +drop this functionality at some point. |
10 | 27 |
|
11 | 28 | ## profiles |
12 | 29 |
|
|
0 commit comments