We needed to protect our production site from prying eyes for a while with a basic authentication. Using apache basic auth settings seemed not enough. Or actually was too much. We wanted the theme to blend in. So these files were not supposed to get protected. Only our Drupal pages should.
With drupal we can enable the locale module and install the i18n module to internationalise and translate our site we can make our hands dirty by visiting the http://build2be.com/admin/build/translate/search.
Still our work is not finished yet. We have to dive into settings.php to translate more strings of our site.
Taken from http://drupal.org/node/275705#comment-1058360 and using http://drupal.org/projects/drush_sm we learn we may choose from a lot of variables.
This book is about what step I took to prepare the (temporary) demo site and what my presentation is about.
Trying best practices I occasionally move the files directory from DRUPAL_ROOT/files/my-site.com to DRUPAL_ROOT/sites/my-sites/files
Doing this has some implications for the files table content. All file-path are pointing to the wrong location.
Quick solution for this is an mysql replace update query.
select replace(filepath, 'files/my-site/', 'sites/my-site/files/') from files;
# update files set filepath=replace(filepath, 'files/my-site/', 'sites/my-site/files/')"Or through drush
These are my notes when doing my first (drupal) presentation @ FrOSCon 2008 Drupal Room
This method uses the concepts
This way an upgrade to another drupal version runs smoothly. Hmmm this was about developer environment.
Why do I need this? To make sites like http://nf.test http://nf.dev or http://froscon.demo
sudo su -
echo 127.0.0.254 froscon.demo >> /etc/hosts