On Tuesday 10 August 2010, Parker Selbert wrote: > Michael Schuerig wrote: > >> I don't see where security would be an issue here, but reusability > >> may be. A more generic "VERSION" file that can be loaded and read > >> from would be available anywhere in your application, and could be > >> simpler to maintain. You could do it as a plaintext file that just > >> reads '1.1.42', or namespace it as MyApp::VERSION etc. > > > > I didn't explain why I want this version number to begin with. I > > don't need the version anywhere in the app. The whole point is to > > identify the version of the app that has generated a page. So, if > > I get a bug report from a tester or user, I can tell them to > > attach the offending page to the bug report and from that I can > > find out what version they were using. > > > > Michael > > Really the idea was that you would remove writing markup as part of > your deploy recipe, and more importantly than that you'd automate > syncing the VERSION with git. > > With this method: > > 1. You have less to remember
I don't follow. What do I have to remember with my current method? > 2. A more orthogonal use of your deploy and layout There I don't feel any guilt. > 3. Can't ever have the incorrect tag in your layout That's the same for both approaches, isn't it? When I deploy a tag, that tag is used to access the git repo and it is written to the partial. Michael -- Michael Schuerig mailto:[email protected] http://www.schuerig.de/michael/ -- 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]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
