I am by no means a Ruby developer but after reading the docs extensively and performing trial & error with ~/.gemrc, gem source -a ..., etc., there does not seem to be a way to set the source registry for the Gemfile that is created for a new project. This prevents Organizations who are unable to reach out to public repos (air-gap) from using the tool completely. By adding the ability to set the source registry, it would allow you to pull Gems from mirrors such as an internal Artifactory.
Motivation
This will enable many Enterprise users who are bound to internal, mirrored registries to be able to use the tool.
Guide-level explanation
I think this could be accomplished in one of (at least) two ways:
add a command line switch to terraspace such as --gem-mirror to indicate an alternate gem source
Summary
I am by no means a Ruby developer but after reading the docs extensively and performing trial & error with
~/.gemrc,gem source -a ..., etc., there does not seem to be a way to set thesourceregistry for theGemfilethat is created for a new project. This prevents Organizations who are unable to reach out to public repos (air-gap) from using the tool completely. By adding the ability to set the source registry, it would allow you to pull Gems from mirrors such as an internal Artifactory.Motivation
This will enable many Enterprise users who are bound to internal, mirrored registries to be able to use the tool.
Guide-level explanation
I think this could be accomplished in one of (at least) two ways:
terraspacesuch as--gem-mirrorto indicate an alternate gem source~/.gemrcReference-level explanation
Drawbacks
Unresolved Questions