The second one looks like it does the right things. I will give it a try.
Thanks for the quick answer!
Horst
Jim Gay schrieb:
> This http://github.com/nelstrom/radiant-file-system-extension
>
> Or my newer preference is my fork of terralien's
> http://github.com/saturnflyer/radiant-file-system-
On 12/13/09 9:53 AM, john muhl wrote:
> heroku has a tool called "taps" that i use for this purpose; it's not
> tied to the heroku service at all so you can use it to push/pull
> databases from any where you like.
>
> http://docs.heroku.com/taps
> http://adamblog.heroku.com/past/2009/2/11/taps_for_
This http://github.com/nelstrom/radiant-file-system-extension
Or my newer preference is my fork of terralien's
http://github.com/saturnflyer/radiant-file-system-resources-extension
On Dec 13, 2009, at 3:06 PM, Horst Rischbode wrote:
> Hello,
>
> I'm new to radiant, so please excuse, if my que
Hello,
I'm new to radiant, so please excuse, if my question is stupid...
Is there a way of holding the layout in seperate files in my application?
As far as I understand, the common way is to hold the layout in the
database. I would prefer to develop my layout with my favourite editor
and then
heroku has a tool called "taps" that i use for this purpose; it's not
tied to the heroku service at all so you can use it to push/pull
databases from any where you like.
http://docs.heroku.com/taps
http://adamblog.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/
On Sun, Dec 13, 2009 at
Hi everybody,
I am developing a blog for a customer using Radiant 0.8.1
What is the usual way of deploying radiant to the production server?
Since lot's of configuration is stored in the database, I need to overwrite
db on the server with my development db (with capistrano it is not a
problem).
Bu
