<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://ceardach.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>deployment</title>
 <link>http://ceardach.com/blog/tags/deployment</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Building a Product on top of Drupal</title>
 <link>http://ceardach.com/blog/2010/02/building-product-top-drupal</link>
 <description>&lt;p&gt;For the past year, all of my Drupal work has been devoted to building a product on top of Drupal.  In the beginning of the year, I worked with the &lt;a href=&quot;http://sciencecollaboration.org/&quot; title=&quot;Enable collaboration between scientists&quot;&gt;Science Collaboration Framework&lt;/a&gt; to create &lt;a href=&quot;http://www.pdonlineresearch.org/&quot; title=&quot;Social collaboration for Parkinson&#039;s Disease research&quot;&gt;PD Online&lt;/a&gt;.  For the past 7 months, I have been with &lt;a href=&quot;http://www.goingon.com/&quot; title=&quot;Drupal for Education: Connect. Engage. Learn.&quot;&gt;GoingOn&lt;/a&gt; building a social education platform on top of Drupal.  I hope I will have the opportunity to tell you everything I have learned at &lt;a href=&quot;http://sf2010.drupal.org&quot; title=&quot;Drupalcon San Francisco 2010&quot;&gt;Drupalcon&lt;/a&gt; in the &lt;a href=&quot;http://sf2010.drupal.org/conference/sessions/building-product-top-drupal&quot; title=&quot;Vote for me?&quot;&gt;Building a Product on top of Drupal&lt;/a&gt; session held by &lt;a href=&quot;http://drupal.org/user/33290&quot; title=&quot;AKA: starbow&quot;&gt;Tao Starbow&lt;/a&gt; and I.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://ceardach.com/blog/2010/02/building-product-top-drupal&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://ceardach.com/blog/2010/02/building-product-top-drupal#comments</comments>
 <category domain="http://ceardach.com/blog/tags/deployment">deployment</category>
 <category domain="http://ceardach.com/blog/tags/development-workflow">development workflow</category>
 <category domain="http://ceardach.com/blog/tags/drupal">drupal</category>
 <category domain="http://ceardach.com/blog/tags/drupalcon">drupalcon</category>
 <category domain="http://ceardach.com/blog/tags/drupalplanet">drupalplanet</category>
 <category domain="http://ceardach.com/blog/tags/version-control">version control</category>
 <pubDate>Tue, 16 Feb 2010 08:52:01 -0800</pubDate>
 <dc:creator>Kathleen</dc:creator>
 <guid isPermaLink="false">10052 at http://ceardach.com</guid>
</item>
<item>
 <title>Learning more about Staging and Deployment</title>
 <link>http://ceardach.com/blog/2009/01/learning-more-about-staging-and-deployment</link>
 <description>&lt;p&gt;Staging and deployment is a vital part of any project, Drupal or not.  As I&#039;ve &lt;a href=&quot;/blog/2008/06/development-environment-drupal&quot; title=&quot;Development Environment for Drupal&quot;&gt;discussed&lt;/a&gt; &lt;a href=&quot;/blog/2008/06/development-production-database-merge-script&quot; title=&quot; A Database Merge Script&quot;&gt;previously&lt;/a&gt;, staging and deploying to production is particularly difficult for all the Content Management Systems out there that intermingle content and configuration settings within the database - and Drupal is definitely one of them.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://ceardach.com/blog/2009/01/learning-more-about-staging-and-deployment&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://ceardach.com/blog/2009/01/learning-more-about-staging-and-deployment#comments</comments>
 <category domain="http://ceardach.com/blog/tags/deployment">deployment</category>
 <category domain="http://ceardach.com/blog/tags/development-workflow">development workflow</category>
 <category domain="http://ceardach.com/blog/tags/drupal">drupal</category>
 <category domain="http://ceardach.com/blog/tags/drupalcon">drupalcon</category>
 <category domain="http://ceardach.com/blog/tags/drupalplanet">drupalplanet</category>
 <category domain="http://ceardach.com/blog/tags/version-control">version control</category>
 <pubDate>Sun, 18 Jan 2009 13:55:45 -0800</pubDate>
 <dc:creator>Kathleen</dc:creator>
 <guid isPermaLink="false">10041 at http://ceardach.com</guid>
</item>
<item>
 <title>dbscripts v1.0 released</title>
 <link>http://ceardach.com/blog/2008/09/dbscripts-v10-released</link>
 <description>&lt;p&gt;I finally decided that what I&#039;ve been developing in the &lt;a href=&quot;http://drupal.org/project/dbscripts/&quot; title=&quot;Bash Scripts for Database Management&quot; class=&quot;external-link&quot;&gt;dbscripts module&lt;/a&gt; is stable and decent enough to deserve an official 1.0 release.  I&#039;ve written up the problem I was trying to solve with these scripts in &lt;a href=&quot;/blog/2008/06/development-production-database-merge-script&quot;&gt;another blog post&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;So what are some improvements I&#039;ve done since I first released it?  Besides refactoring and cleaning up the code, I have added:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://ceardach.com/blog/2008/09/dbscripts-v10-released&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://ceardach.com/blog/2008/09/dbscripts-v10-released#comments</comments>
 <category domain="http://ceardach.com/blog/tags/deployment">deployment</category>
 <category domain="http://ceardach.com/blog/tags/development-workflow">development workflow</category>
 <category domain="http://ceardach.com/blog/tags/drupal">drupal</category>
 <category domain="http://ceardach.com/blog/tags/drupalplanet">drupalplanet</category>
 <category domain="http://ceardach.com/blog/tags/version-control">version control</category>
 <pubDate>Fri, 19 Sep 2008 15:36:49 -0700</pubDate>
 <dc:creator>Kathleen</dc:creator>
 <guid isPermaLink="false">10032 at http://ceardach.com</guid>
</item>
<item>
 <title>Development Environment for Drupal</title>
 <link>http://ceardach.com/blog/2008/06/development-environment-drupal</link>
 <description>&lt;p&gt;There are virtually an unlimited amount of ways to set up a development environment, and it all depends upon your project&#039;s individual needs and your preferred workflow.  Sometimes, though, it just takes experience and exposure to other ideas to figure out what would be best.  So, here is a description of my development environment.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://ceardach.com/blog/2008/06/development-environment-drupal&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://ceardach.com/blog/2008/06/development-environment-drupal#comments</comments>
 <category domain="http://ceardach.com/blog/tags/deployment">deployment</category>
 <category domain="http://ceardach.com/blog/tags/development-workflow">development workflow</category>
 <category domain="http://ceardach.com/blog/tags/drupal">drupal</category>
 <category domain="http://ceardach.com/blog/tags/drupalplanet">drupalplanet</category>
 <category domain="http://ceardach.com/blog/tags/version-control">version control</category>
 <pubDate>Thu, 26 Jun 2008 14:33:44 -0700</pubDate>
 <dc:creator>Kathleen</dc:creator>
 <guid isPermaLink="false">10026 at http://ceardach.com</guid>
</item>
<item>
 <title>Development to Production: A Database Merge Script</title>
 <link>http://ceardach.com/blog/2008/06/development-production-database-merge-script</link>
 <description>&lt;p&gt;Migrating changes from development to production is particularly tricky in Drupal due to a large amount of configuration settings being stored within the database.  &lt;a href=&quot;http://boston2008.drupalcon.org/session/updating-and-upgrading-live-sites&quot; title=&quot;Updating and upgrading live sites Birds of a Feather&quot; class=&quot;external-link&quot;&gt;Attendees of Drupalcon 2008&lt;/a&gt; made it clear that this is a particularly annoying problem.  I attended the &lt;a href=&quot;http://boston2008.drupalcon.org/session/drupalcon-tutorial-best-practices-development-environments-staging-build-management-and-prod&quot; title=&quot;Best practices in development environments, staging, build management, and production environments&quot; class=&quot;external-link&quot;&gt;Development / Test / Production Environments&lt;/a&gt; panel to learn about how the big guys (including Drupal.org itself) manage deploying their sites from one working space to the next.  We were disappointed to discover that even the big guys are currently writing down all the steps to upgrade and simply performing them on the production server.&lt;/p&gt;

&lt;p&gt;This method poses several problems due to the Human Element being involved in the entire process.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://ceardach.com/blog/2008/06/development-production-database-merge-script&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://ceardach.com/blog/2008/06/development-production-database-merge-script#comments</comments>
 <category domain="http://ceardach.com/blog/tags/database">database</category>
 <category domain="http://ceardach.com/blog/tags/deployment">deployment</category>
 <category domain="http://ceardach.com/blog/tags/development-workflow">development workflow</category>
 <category domain="http://ceardach.com/blog/tags/drupal">drupal</category>
 <category domain="http://ceardach.com/blog/tags/drupalplanet">drupalplanet</category>
 <category domain="http://ceardach.com/blog/tags/version-control">version control</category>
 <pubDate>Mon, 23 Jun 2008 10:35:20 -0700</pubDate>
 <dc:creator>Kathleen</dc:creator>
 <guid isPermaLink="false">10018 at http://ceardach.com</guid>
</item>
</channel>
</rss>
