I have been off the list for a while but using rails, radiant and
spree for several years. Looking through many recent items on the mail
list, I think that I can identify a common theme that has not been
addresed. I only noticed this because I set up a new rvm environment
using 1.8.7 to run radiant and I did not have the gems locally. Since
github makes it very easy for new people to access the source (good),
the mails indicate that many people are first trying to install and
run radiant from a cloned radiant/radiant source tree (bad). Even
though it is certainly not the best way to get started, we could try
to make this easier for them, or provide hints to put them on the
right path.

For example, if a newb clones/downloads the radiant source tree, cds
to radiant and then runs bundle install, it appears to work! He/she
gets a nice message saying 'Your bundle is complete' but it is not
truly ready for use. Then running 'bundle exec rake production
db:bootstrap' as in the readme gets the next error message, which is
'no such file to load -- radius' because the bundle isn't designed for
this purpose. It doesn't include radiant as a gem, which pulls in the
other dependencies.

We could:-

1) Include remarks in the readme and install files saying that it
probably should not be run from the source tree :-) and advising them
to install the radiant gem

2) include another file like a development Gemfile that contains the
full list of dependencies and providing a hint to newbs that they
should rename and use the longer file if they want to run from the

3) I know it sucks, but if we included a database.yml file (not just
the templates like database.sqlite.yml), it would be one thing less
for a novice to do

David V.

PS I hope that the for,atting works out this time!

Reply via email to