<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Postgres on Nyghtowl</title>
    <link>https://nyghtowl.com/tags/postgres/</link>
    <description>Recent content in Postgres on Nyghtowl</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc-sa/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC-SA 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Sun, 15 Sep 2013 01:24:02 +0000</lastBuildDate>
    <atom:link href="https://nyghtowl.com/tags/postgres/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Flask, Heroku &amp; Alembic Play Together</title>
      <link>https://nyghtowl.com/posts/2013/09/how-flask-heroku-alembic-play-together/</link>
      <pubDate>Sun, 15 Sep 2013 01:24:02 +0000</pubDate>
      <guid>https://nyghtowl.com/posts/2013/09/how-flask-heroku-alembic-play-together/</guid>
      <description>&lt;p&gt;I just spent a couple days getting up to speed on database migrations in general, how to make it work with Flask and Postgres and how to make them work on Heroku. There is some information out there but it took a little time hunting down what I needed; thus, I’ve summarized some of the main steps to help get others up and running with Flask, Heroku and Alembic.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Why migrate?&lt;/strong&gt; Best practice is to avoid recreating your database(s). Usually you just want to make changes to the existing database(s) and track those changes. If at any time you need to go back to a previous version, the migration docs will help you easily revert to an old version / schema and then upgrade back to the most recent depending on your needs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
