<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Rails deploy using sqlite3</title>
	<atom:link href="http://www.bagonca.com/blog/2009/05/09/rails-deploy-using-sqlite3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bagonca.com/blog/2009/05/09/rails-deploy-using-sqlite3/</link>
	<description>Yet another developer blog</description>
	<lastBuildDate>Mon, 19 Dec 2011 21:48:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jeremie</title>
		<link>http://www.bagonca.com/blog/2009/05/09/rails-deploy-using-sqlite3/comment-page-1/#comment-408</link>
		<dc:creator>Jeremie</dc:creator>
		<pubDate>Fri, 02 Dec 2011 16:40:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=394#comment-408</guid>
		<description>Also, i had to adapt the hooks :
after &quot;deploy:update&quot;, &quot;sqlite3:link_configuration_file&quot;

instead of after deploy:migrate

Reason is that when you just deploy without migration, you would have a release path without database.yml
(database.yml is supposed to be removed from the source code).</description>
		<content:encoded><![CDATA[<p>Also, i had to adapt the hooks :<br />
after &#8220;deploy:update&#8221;, &#8220;sqlite3:link_configuration_file&#8221;</p>
<p>instead of after deploy:migrate</p>
<p>Reason is that when you just deploy without migration, you would have a release path without database.yml<br />
(database.yml is supposed to be removed from the source code).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremie</title>
		<link>http://www.bagonca.com/blog/2009/05/09/rails-deploy-using-sqlite3/comment-page-1/#comment-407</link>
		<dc:creator>Jeremie</dc:creator>
		<pubDate>Fri, 02 Dec 2011 16:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=394#comment-407</guid>
		<description>Thanks, very useful!
I had to adapt this :
in sqlite3:link_configuration_file, use the current_path and not the release path, with a cap deploy migrate only, the release path seem to be incorrect.

    run &quot;ln -nsf #{shared_database_path}/sqlite_config.yml #{current_path}/config/database.yml&quot;</description>
		<content:encoded><![CDATA[<p>Thanks, very useful!<br />
I had to adapt this :<br />
in sqlite3:link_configuration_file, use the current_path and not the release path, with a cap deploy migrate only, the release path seem to be incorrect.</p>
<p>    run &#8220;ln -nsf #{shared_database_path}/sqlite_config.yml #{current_path}/config/database.yml&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by CoBPEZ</title>
		<link>http://www.bagonca.com/blog/2009/05/09/rails-deploy-using-sqlite3/comment-page-1/#comment-61</link>
		<dc:creator>Twitted by CoBPEZ</dc:creator>
		<pubDate>Sun, 10 May 2009 10:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=394#comment-61</guid>
		<description>[...] This post was Twitted by CoBPEZ - Real-url.org [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by CoBPEZ &#8211; Real-url.org [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

