Sha256: d85bd8a9c802b306f3458635a57050503fb7c2493b226e05adaeb8465b797099
Contents?: true
Size: 594 Bytes
Versions: 44
Compression:
Stored size: 594 Bytes
Contents
<%# I'm thinking that creating test ACS remotes is not worth it for HTTP proxies because
we're editing 'n' remotes rather than just one. At sync time, if a remote fails to
update, the user can look at the error in Dynflow and likely figure out that something
is wrong with the HTTP proxy config. %>
<%= select_f(f, :http_proxy_id, ::HttpProxy.all, :id, :name, {:include_blank => true}, {:label => _("Alternate Content Source HTTP Proxy"),
:label_help => _('Traffic for all alternate content sources associated with this smart proxy will go through the chosen HTTP proxy.')}) %>
Version data entries
44 entries across 44 versions & 1 rubygems