<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Docker on Nick Perkins</title>
    <link>https://nickperkins.au/tags/docker/</link>
    <description>Recent content in Docker on Nick Perkins</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 21 Jul 2019 12:57:05 +1000</lastBuildDate>
    <atom:link href="https://nickperkins.au/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using pyodbc in AWS Lambda functions</title>
      <link>https://nickperkins.au/code/lamda-pyodbc/</link>
      <pubDate>Sun, 21 Jul 2019 12:57:05 +1000</pubDate>
      <guid>https://nickperkins.au/code/lamda-pyodbc/</guid>
      <description>This week I was working on an AWS Lambda function that needed to read and write from a legacy Microsoft SQL database. It&amp;rsquo;s written using the AWS Chalice framework and in local testing everything looked great. Not so much when we needed to deploy it to AWS for testing.&#xA;Why? Most of the time that you include a python package for use in a lambda function, Chalice is able to package that into the deployment, and you&amp;rsquo;re good to go.</description>
    </item>
  </channel>
</rss>
