I’m planning to use radiant to power a website, but before taking the
plunge I have some questions. I installed the 0.6 release candidate.
Here are questions I couldn’t answer by looking at the docs or the
mailing list archive:
an applicaiton created with the radiant command doesn’t apparently
contain the radiant code. Is there a way to freeze it to the gems used
like for rails applications? (I saw in environment.rb that the gem
used is referenced) I didn’t see it in the rake tasks available.
a related question: Will there be attention paid to upgrade
procedures to future versions? I’d like to follow the latest release,
but won’t be able to afford long downtimes.
Having all templates and layouts in the database is not the most
user friendly to edit. Only for my tests I have lost time because the
‘Save and continue editing’ looses the position of my cursor when the
page reload. Is there a way to store layouts in files? An “ajax” way
of saving the changes when editing in the browser would be a
workaround. I would still prefer templates in files (that way, if you
want to change the design, you can do it in development on all layouts
to be changed, and have it all transfered at once, to the production
server. In this case I find it much easier to sync files and
directories than DBs)
If I want to let people register on the site, what’s the best way to
do it? Add a controller in the radiant installation? Run an additional
rails app to just handle this?
Thanks in advance for your help.