[Rails-core] Convention over configuration and the Rails.root-tmp-folder
Hi,
I started to write a tiny rails app which comes completely as a ruby gem.
Since this app has a big cousin in rails I did not want to use another
framework like sinatra.
Since the app is a gem, I do not want it to store runtime-files in the
tmp-folder. So I thought I should not stay with the convention but
configure the location of the tmp-folder. But as far as I can see, there is
no way to configure it.
I searched the source code and found lines like this one:
./railties/lib/rails/application/configuration.rb:
@cache_store = [ :file_store, #{root}/tmp/cache/ ]
As one can see, the tmp-folder does not follow convention over
configuration but is hard coded.
So what about adding a configuration option? I am using Rails 4.1.
Regards
Thomas
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Rails-core] Convention over configuration and the Rails.root-tmp-folder
You're contradicting yourself. The /tmp folder is 100% convention and 0%
configuration. Therefore it's all convention over configuration. :)
On Tue, Feb 11, 2014 at 1:11 PM, Thomas V. Worm t...@s4r.de wrote:
Hi,
I started to write a tiny rails app which comes completely as a ruby gem.
Since this app has a big cousin in rails I did not want to use another
framework like sinatra.
Since the app is a gem, I do not want it to store runtime-files in the
tmp-folder. So I thought I should not stay with the convention but
configure the location of the tmp-folder. But as far as I can see, there is
no way to configure it.
I searched the source code and found lines like this one:
./railties/lib/rails/application/configuration.rb:
@cache_store = [ :file_store, #{root}/tmp/cache/ ]
As one can see, the tmp-folder does not follow convention over
configuration but is hard coded.
So what about adding a configuration option? I am using Rails 4.1.
Regards
Thomas
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Rails-core] Convention over configuration and the Rails.root-tmp-folder
;-)
I understand convention over configuration not the same as you do: you do
not need to configure if your are fine with the convention, but you can, if
you want or must. Like in ActiveRecord, when the table names can be derived
from the class names but can also be declared, when you have a legacy db.
Am Dienstag, 11. Februar 2014 19:52:15 UTC+1 schrieb Andrew Kaspick:
You're contradicting yourself. The /tmp folder is 100% convention and 0%
configuration. Therefore it's all convention over configuration. :)
On Tue, Feb 11, 2014 at 1:11 PM, Thomas V. Worm t...@s4r.de javascript:
wrote:
Hi,
I started to write a tiny rails app which comes completely as a ruby gem.
Since this app has a big cousin in rails I did not want to use another
framework like sinatra.
Since the app is a gem, I do not want it to store runtime-files in the
tmp-folder. So I thought I should not stay with the convention but
configure the location of the tmp-folder. But as far as I can see, there is
no way to configure it.
I searched the source code and found lines like this one:
./railties/lib/rails/application/configuration.rb:
@cache_store = [ :file_store, #{root}/tmp/cache/ ]
As one can see, the tmp-folder does not follow convention over
configuration but is hard coded.
So what about adding a configuration option? I am using Rails 4.1.
Regards
Thomas
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-co...@googlegroups.com javascript:.
To post to this group, send email to
rubyonra...@googlegroups.comjavascript:
.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Rails-core] Convention over configuration and the Rails.root-tmp-folder
On Feb 11, 2014, at 3:11 PM, Thomas V. Worm t...@s4r.de wrote:
;-)
I understand convention over configuration not the same as you do: you do not
need to configure if your are fine with the convention, but you can, if you
want or must. Like in ActiveRecord, when the table names can be derived from
the class names but can also be declared, when you have a legacy db.
The configuration is one level higher, when you pick a cache_store:
config.cache_store = :file_store, /path/to/cache/directory
(from the caching guide)
--Matt Jones
Am Dienstag, 11. Februar 2014 19:52:15 UTC+1 schrieb Andrew Kaspick:
You're contradicting yourself. The /tmp folder is 100% convention and 0%
configuration. Therefore it's all convention over configuration. :)
On Tue, Feb 11, 2014 at 1:11 PM, Thomas V. Worm t...@s4r.de wrote:
Hi,
I started to write a tiny rails app which comes completely as a ruby gem.
Since this app has a big cousin in rails I did not want to use another
framework like sinatra.
Since the app is a gem, I do not want it to store runtime-files in the
tmp-folder. So I thought I should not stay with the convention but configure
the location of the tmp-folder. But as far as I can see, there is no way to
configure it.
I searched the source code and found lines like this one:
./railties/lib/rails/application/configuration.rb:@cache_store
= [ :file_store, #{root}/tmp/cache/ ]
As one can see, the tmp-folder does not follow convention over configuration
but is hard coded.
So what about adding a configuration option? I am using Rails 4.1.
Regards
Thomas
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-co...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Rails-core] Convention over configuration and the Rails.root-tmp-folder
But it's very easy to change:
In your app's configuration.rb
config.cache_store = :file_store, /path/to/cache/directory
2014-02-11 17:11 GMT-03:00 Thomas V. Worm t...@s4r.de:
;-)
I understand convention over configuration not the same as you do: you do
not need to configure if your are fine with the convention, but you can, if
you want or must. Like in ActiveRecord, when the table names can be derived
from the class names but can also be declared, when you have a legacy db.
Am Dienstag, 11. Februar 2014 19:52:15 UTC+1 schrieb Andrew Kaspick:
You're contradicting yourself. The /tmp folder is 100% convention and 0%
configuration. Therefore it's all convention over configuration. :)
On Tue, Feb 11, 2014 at 1:11 PM, Thomas V. Worm t...@s4r.de wrote:
Hi,
I started to write a tiny rails app which comes completely as a ruby
gem. Since this app has a big cousin in rails I did not want to use another
framework like sinatra.
Since the app is a gem, I do not want it to store runtime-files in the
tmp-folder. So I thought I should not stay with the convention but
configure the location of the tmp-folder. But as far as I can see, there is
no way to configure it.
I searched the source code and found lines like this one:
./railties/lib/rails/application/configuration.rb:
@cache_store = [ :file_store, #{root}/tmp/cache/ ]
As one can see, the tmp-folder does not follow convention over
configuration but is hard coded.
So what about adding a configuration option? I am using Rails 4.1.
Regards
Thomas
--
You received this message because you are subscribed to the Google
Groups Ruby on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send
an email to rubyonrails-co...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an
email to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
--
Bruno Bonamin.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.
[Rails-core] Suggestion: Use issuetemplate.com to make issue triaging easier.
I posted this on GitHub as an issuehttps://github.com/rails/rails/issues/14019#issuecomment-34801491, and was asked to post it here instead: I made a web app for the AngularJS project to help them triage their huge amounts of issues they have to deal with. I noticed your project gets a lot of issues as well and thought you could find it useful. Give it a look and feel free to ask me any questions or submit issues to the repository. *http://issuetemplate.com/ http://issuetemplate.com/* What do you think? Let me know if you have any questions about how this works. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
