<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering on Gophish - Blog</title>
    <link>https://getgophish.com/blog/tags/engineering/</link>
    <description>Recent content in Engineering on Gophish - Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Feb 2016 07:00:00 -0600</lastBuildDate>
    
	<atom:link href="https://getgophish.com/blog/tags/engineering/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Handling Database Migrations in Go</title>
      <link>https://getgophish.com/blog/post/database-migrations-in-go/</link>
      <pubDate>Mon, 01 Feb 2016 07:00:00 -0600</pubDate>
      
      <guid>https://getgophish.com/blog/post/database-migrations-in-go/</guid>
      <description>&amp;ldquo;I got my database schema correct on the first try.&amp;rdquo;
-No one ever.
 Like most big projects, gophish needed a way to automatically manage changes to our database schema. As new features were being added, we found ourselves in a situation that required us to add or modify columns and tables to store the new data.
In a hosted environment, this is no problem since we control the database and can make schema changes as we see fit.</description>
    </item>
    
  </channel>
</rss>