1. 16 11月, 2019 2 次提交
  2. 27 10月, 2019 1 次提交
  3. 11 10月, 2019 1 次提交
  4. 04 10月, 2019 1 次提交
  5. 28 9月, 2019 1 次提交
  6. 27 9月, 2019 1 次提交
  7. 26 9月, 2019 1 次提交
  8. 20 9月, 2019 1 次提交
  9. 30 8月, 2019 1 次提交
  10. 28 8月, 2019 1 次提交
  11. 20 8月, 2019 1 次提交
  12. 15 8月, 2019 4 次提交
  13. 09 8月, 2019 1 次提交
  14. 05 8月, 2019 1 次提交
  15. 29 7月, 2019 1 次提交
  16. 26 7月, 2019 1 次提交
  17. 25 7月, 2019 3 次提交
  18. 23 7月, 2019 3 次提交
  19. 11 7月, 2019 2 次提交
  20. 28 6月, 2019 1 次提交
  21. 17 6月, 2019 2 次提交
  22. 14 6月, 2019 5 次提交
  23. 13 6月, 2019 1 次提交
  24. 05 6月, 2019 1 次提交
    • M
      Preserve Bundle configuration during app generation (#34755) · b1464e34
      Marco Costa 提交于
      When generating a new rails application (rails new) using a custom template that
      includes gems from an authenticated source, the user has to provide credentials to
      bundler.
      
      One way to do this is by exporting environment variables, for example:
      
      export BUNDLE_GITHUB__COM=user:pass: provides credentials for bundler to fetch
      gems from github.com.
      
      The problem this PR addresses is that we are currently scrubs all /BUNDLE_.*/
      environment variables by wrapping our system calls in Bundler.with_clean_env.
      
      We do this because we don't want our commands executed against the generated project
      to use the generator's bundler environment (e.g. our gems): the generated project should
      use it's own configuration.
      
      The problem with Bundler.with_clean_env is that, on top of restoring environment
      variables to their original state, it also scrubs any /BUNDLE_.*/ variables, which is harmful for authenticated gem sources.
      
      This PR replaces Bundler.with_clean_env with Bundler.with_original_env, which only
      restores environment variables to their initial state, without additional scrubbing.
      b1464e34
  25. 15 5月, 2019 1 次提交
  26. 08 5月, 2019 1 次提交