Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
This comment has been deleted
👋🏼 @dwf
I also did some googling and couldn’t find anything. Although I did find this workaround—check it out: https://stackoverflow.com/a/56639755. It will let you store your GitHub access token in an environment variable.
Another option might be to mirror the packages to a private npm registry, and use yarnrc to read the credentials from an env var: https://yarnpkg.com/configuration/yarnrc
Same here :-/
Dependency’s repo access is explicitely authorized to DigitalOcean (I could deploy that repo as an app on its own) but when yarn/npm fetches it as a dependency, it fails to authenticate.
Using a Github token is a very crappy solution, as the token gives read/write access to all repos.