Do not undesten what's the reason to have such constants. Site users send there requests with domain name and you can get it in "request.host" or other ActionController <http://apidock.com/rails/ActionController>::Request<http://apidock.com/rails/ActionController/Request> methods. If you needed dynamical behavior then you should refuse constants and use methods or variables.
четверг, 24 января 2013 г., 23:00:19 UTC+4 пользователь Ben Densmore написал: > > Our app currently has some constants set in the environment.rb file using > Object.const_set "ProductionDomain", "mydomain.com" and some other domain > related constants that are based off of this initial constant. > > We are now going to be offering a .fr domain in addition to .com so I need > to make these constants dynamic based on which TLD a person may be on. > > My thought was that maybe I should move these constants into their own > file in the initializers folder and can then check whether the user is on > the .com TLD or .fr > > Is there a better way to handle this? I couldn't find a way to do it in > the environment.rb file so I'm thinking this other approach may be the way > to go. > > We are on Rails 2.3.14, so any options need to be compatible with that > version. > > Thank you, > Ben > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/H6rto19j2XIJ. For more options, visit https://groups.google.com/groups/opt_out.
