<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tutorial on Townsourced Tech Blog</title>
    <link>https://tech.townsourced.com/tags/tutorial/</link>
    <description>Recent content in Tutorial on Townsourced Tech Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.</copyright>
    <lastBuildDate>Sun, 15 Jan 2017 19:05:51 -0600</lastBuildDate>
    
	<atom:link href="https://tech.townsourced.com/tags/tutorial/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Anatomy of a Go Web App - Part 2: Authentication</title>
      <link>https://tech.townsourced.com/post/anatomy-of-a-go-web-app-authentication/</link>
      <pubDate>Sun, 15 Jan 2017 19:05:51 -0600</pubDate>
      
      <guid>https://tech.townsourced.com/post/anatomy-of-a-go-web-app-authentication/</guid>
      <description>&lt;p&gt;This is part two of a set of posts breaking down some of the decisions I made when putting together the web server for
&lt;a href=&#34;https://www.townsourced.com&#34;&gt;townsourced&lt;/a&gt;.  The first part is &lt;a href=&#34;https://tech.townsourced.com/post/anatomy-of-a-go-web-app/&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Instead of a general overview, like part one, this post will focus specifically on &lt;strong&gt;User Authentication&lt;/strong&gt;, i.e. how to
handle passwords (if at all) and session management.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Anatomy of a Go Web Application</title>
      <link>https://tech.townsourced.com/post/anatomy-of-a-go-web-app/</link>
      <pubDate>Sun, 04 Dec 2016 10:37:07 -0600</pubDate>
      
      <guid>https://tech.townsourced.com/post/anatomy-of-a-go-web-app/</guid>
      <description>&lt;p&gt;When building a web application from scratch, there are a lot of decisions to make.  The goal of this guide is to give
one more example of how you can go about building a web application in the Go language, as well as to give you an idea
what things you need to start thinking about and plan for before you get started.&lt;/p&gt;

&lt;p&gt;This guide is not intended to be exhaustive, nor is it absolute. It is a compendium of the things I thought about and how I dealt
with them when building &lt;a href=&#34;https://www.townsourced.com&#34;&gt;townsourced.com&lt;/a&gt;.  Hopefully you&amp;rsquo;ll find it useful.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>