Recent self-hosting improvements in Turborepo core

[anthonyshew]

Hi from Turborepo core team!

Someone recently flagged for me that authenticating using self-hosted caches was a terrible experience. I eventually found this page in the documentation for this project, and...well, I didn't even like reading it, so I can't imagine how annoying it was to use.

I didn't know about this, and don't know how it got that way, but we took a moment to make sure it's better than it was.

Check out the new --manual flag and the updates on the self-hosting docs to see the new usage. The configuration files and settings in turbo.json should get handled for users automatically now.

If you have any feedback for us on how to make this better, please let us know!

Note

I love making open-source PRs, and would have here, but felt uncomfortable making one here because I'm not a user of this code. I've always said "make PRs to projects you use", so trying to follow my own advice. 😄

[fox1t]

Hey! @anthonyshew, thanks for pointing this out. I recently discovered that new feature on your side and was also interested in exploring the custom URL login flow. Do you have any documentation on routes that a custom caching server needs to implement to be compatible with the turbo login—-api=https://acme.com/api command?

The login process was the major pain point for our users since day one.