Re: [Radiant] Backup
On Tue, Sep 8, 2009 at 6:17 AM, john muhl johnm...@gmail.com wrote: it depends on how what sort of database you're using. if it's sqlite you can simply zip up the entire radiant project and call that a backup. if it's mysql or something else you can use that db's dump/import tools plus a zip file of the radiant project to create a backup. version control also works well for rolling back the project directory (and database if you're using sqlite). 2009/9/7 María Paula Mariani paulamari...@gmail.com: Hello! I'd like to know which is the best way to freeze or to make a backup of my project made in Radiant. I'd like to try some extensions and I'd like to have a backup just in case something goes wrong. How is the best way to restore the project and database (from a backup)? Thanks very much! -- Paula ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant Hi! Thanks very much for your help. I wonder if rake db:schema:dump would help to make a mysql backup. I think it just works for deployment. I wonder if there is some explanation about backups between the documentation, I couldn't find any at least at GIT repository. I've also found this resource: http://blog.radixhound.com/2008/4/28/backing-up-radiant-cms-using-sqlite3 but I don't know if it will work for a mysql database. Considering this, I've made a .tar.gz of my whole radiant directory, including /config. I would like to make that db:dump (which is the correct command?) to create the db backup but I don't know which command is it and which is the name of the database radiant is creating per default when we create a project. Your help will be truly appreciated! Thanks very much, Paula -- Paula ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Backup
2009/9/9 María Paula Mariani paulamari...@gmail.com: Considering this, I've made a .tar.gz of my whole radiant directory, including /config. I would like to make that db:dump (which is the correct command?) to create the db backup but I don't know which command is it and which is the name of the database radiant is creating per default when we create a project. you can find your database connection information inside the config/database.yml file. you're probably most interested in the production database settings; unless of course you have other environments you'd like to backup. for mysql you'll need to run a terminal command such as: mysqldump -u mysql_user your_radiant_db_name dump.mysql.db or: mysqldump -u mysql_user -p your_radiant_db_name dump.mysql.db if the mysql_user requires a password to connect to the db. see http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html for the full documentation. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Backup
On Sep 9, 2009, at 7:14 AM, María Paula Mariani wrote: On Tue, Sep 8, 2009 at 6:17 AM, john muhl johnm...@gmail.com wrote: it depends on how what sort of database you're using. if it's sqlite you can simply zip up the entire radiant project and call that a backup. if it's mysql or something else you can use that db's dump/import tools plus a zip file of the radiant project to create a backup. version control also works well for rolling back the project directory (and database if you're using sqlite). 2009/9/7 María Paula Mariani paulamari...@gmail.com: Hello! I'd like to know which is the best way to freeze or to make a backup of my project made in Radiant. I'd like to try some extensions and I'd like to have a backup just in case something goes wrong. How is the best way to restore the project and database (from a backup)? Thanks very much! -- Paula Hi! Thanks very much for your help. I wonder if rake db:schema:dump would help to make a mysql backup. I think it just works for deployment. I wonder if there is some explanation about backups between the documentation, I couldn't find any at least at GIT repository. Backing up your database is up to you; it is not a part of Radiant. If you're on mysql, try msqldump -u yourusername -p yourpassword -d yourdatabase yourdumpfile.sql I've also found this resource: http://blog.radixhound.com/2008/4/28/backing-up-radiant-cms-using-sqlite3 but I don't know if it will work for a mysql database. I haven't tried that, but you may want to look into the taps gem: http://adam.blog.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/ Considering this, I've made a .tar.gz of my whole radiant directory, including /config. I would like to make that db:dump (which is the correct command?) to create the db backup but I don't know which command is it and which is the name of the database radiant is creating per default when we create a project. I would assume that rake db:dump would be the command to use, but I haven't used it. If you've downloaded and installed the plugin from the blog.radixhound.com site, then it probably has some documentation, or you should at least be able to see the rake tasks it provides. The database that it will use will be listed in your config/ database.yml file. You should consider brushing up on Rails at http://guide.rails.info/ You might also want to look into http://ext.radiantcms.org/extensions/43-super-export Your help will be truly appreciated! Thanks very much, Paula Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] extension dependencies in ray
On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs seancri...@gmail.com wrote: Looks like it's time for another release of Radiant: WHAT'S NEW IN THIS RELEASE? * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] extension dependencies in ray
This is a *runtime* dependency, not an install-time one. Basically, an extension can do this: extension_config do |config| config.extension paperclipped end The initializer will check that paperclipped is available in the app and error out if not. Sean john muhl wrote: On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs seancri...@gmail.com wrote: Looks like it's time for another release of Radiant: WHAT'S NEW IN THIS RELEASE? * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] extension dependencies in ray
thanks for the details. guess that code stays for now. On Wed, Sep 9, 2009 at 1:32 PM, Sean Cribbs seancri...@gmail.com wrote: This is a *runtime* dependency, not an install-time one. Basically, an extension can do this: extension_config do |config| config.extension paperclipped end The initializer will check that paperclipped is available in the app and error out if not. Sean john muhl wrote: On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs seancri...@gmail.com wrote: Looks like it's time for another release of Radiant: WHAT'S NEW IN THIS RELEASE? * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Help with RAILS_ROOT and Frozen Gems
I just tried installing radiant 0.8.1 and all went well until I performed a rake radiant:freeze:gems Now starting mongrel on my development machine produces the following error: ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... my_project/vendor/radiant/vendor/rails/railties/lib/initializer.rb:902:in `read': No such file or directory - my_project/vendor/radiant/config/database.yml (Errno::ENOENT) from my_project/vendor/radiant/vendor/rails/railties/lib/initializer.rb:902:in `database_configuration' from my_project/vendor/radiant/vendor/rails/railties/lib/initializer.rb:437:in `initialize_database' from my_project/vendor/radiant/vendor/rails/railties/lib/initializer.rb:141:in `process' from my_project/vendor/radiant/vendor/rails/railties/lib/initializer.rb:113:in `send' from my_project/vendor/radiant/vendor/rails/railties/lib/initializer.rb:113:in `run' from my_project/vendor/radiant/lib/radiant/initializer.rb:148:in `run' from my_project/vendor/radiant/config/environment.rb:12 from .../ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' ... 12 levels... from ...\ruby\bin\mongrel_rails:19:in `load' from ...\ruby\bin\mongrel_rails:19 from -e:2:in `load' from -e:2 If I step through the initializer.rb, it clearly thinks the RAILS_ROOT should be my_project/vendor/radiant I can make it happy by copying my database.yml to where it's looking, but then the app wants my development.sqlite3.db in the radiant directory and it creates a tmp/ directory for the cache down in vendor/radiant/ too. What am I missing? -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant