Jan David
Jan David
@MrMic The last command works and does exactly what it is supposed to do, namely return `HTTP 404` since there is no content hosted at the root of that domain...
For the folks with the SSL error, can you run `curl` with verbose output? That might reveal more details about the kind of SSL error: ```shell curl -Iv https://index.crates.io/config.json ```
Can you run `curl -Iv https://index.crates.io/config.json` to get more details on the SSL error?
This is slightly more involved, since we also need to change the configuration in [`rust-lang/team`](https://github.com/rust-lang/team/blob/master/repos/rust-lang/keyword-generics-initiative.toml). I'll prepare a PR so that we can change the name in both the repo...
@dependabot rebase
@dependabot rebase
@dependabot rebase
In https://github.com/rust-lang/simpleinfra/pull/389#discussion_r1513232655, it was pointed out that the [developer guide for `rustc`](https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc) suggests creating a `build-rust-analyzer` directory. We might want to clean that up in the future, too.
https://github.com/rust-lang/simpleinfra/pull/110 has been merged and setting the Git username and email is now part of the `init.sh` script.
This might be better as its own issue, but another aspect here is that adding trailing commas to files that have the `.json` ending, but are inferred to support `jsonc`...