You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we only support hardcoded support for github artifact download urls, which makes installers gated behind github. We can solve this by just letting the user specify. This should possibly support some amount of templating, as seen in the config for cargo-binstall.
interesting. this feels complicated- but complicated is fine if the end users are advanced. can we offer a way for an end user to validate/test what they've set up?
Currently we only support hardcoded support for github artifact download urls, which makes installers gated behind github. We can solve this by just letting the user specify. This should possibly support some amount of templating, as seen in the config for cargo-binstall.
It might also help github enterprise users.
Theoretical usecases:
artifact-download-url = "{repo}/releases/downloads/{tag}/"
(what we currently do for github)artifact-download-url = "https://mywebsite.com/{tag}/"
Exposing things like "app-name" and "app-version" are sketchier with workspaces but we can maybe allow them for single-app workspaces?
The text was updated successfully, but these errors were encountered: