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
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.
;-)
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
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
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
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
