<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Josh Millstein</title>
    <description>The latest articles on DEV Community by Josh Millstein (@josh_millstein_7919becd0e).</description>
    <link>https://dev.to/josh_millstein_7919becd0e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2153415%2F9b9868fa-bfb8-44ec-a239-410dc06f0e2c.jpg</url>
      <title>DEV Community: Josh Millstein</title>
      <link>https://dev.to/josh_millstein_7919becd0e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/josh_millstein_7919becd0e"/>
    <language>en</language>
    <item>
      <title>Open source ticketing web application</title>
      <dc:creator>Josh Millstein</dc:creator>
      <pubDate>Tue, 17 Nov 2026 20:18:39 +0000</pubDate>
      <link>https://dev.to/josh_millstein_7919becd0e/open-source-ticketing-web-application-59ap</link>
      <guid>https://dev.to/josh_millstein_7919becd0e/open-source-ticketing-web-application-59ap</guid>
      <description>&lt;p&gt;I’ve spent the last couple years chipping away at building IndieTix (&lt;a href="https://github.com/indieTix-net/indietix" rel="noopener noreferrer"&gt;https://github.com/indieTix-net/indietix&lt;/a&gt;), an open source ticketing app for the venue I run (Liberty Hall, Lawrence, KS). It’s still a work in progress, but we use it every day for all our cinema ticket sales as well as some of our smaller events. I started it thinking I could reduce ticketing fees and consolidate a few ticketing systems we already used for events and cinema. Lots more benefits became clear once I started getting into the project (listed in the README). I also wanted to create something that could be spun up easily for other independent venues and promoters to use: a system that was scalable, secure, cheap, open, and easy to maintain. I built it to work with our Square website and POS system (consolidation of systems for us). I didn’t want to build out an inventory or payment processing tool initially, so using what Square had already refined seemed like a good idea to me. I also didn’t want the added security issues that come from handling payment data, etc. One thing I think would be amazing is if I could get some other inventory/payment processing integrations (Lightspeed, Stripe, etc.). A native inventory and processing system would also make IndieTix fully independent, but for now I’m holding off because of the added security/privacy overhead. You can stand up a complete deployment with a single command, and there are lots of infrastructure tools intended to make it easy to modify, build, tear down and more.&lt;/p&gt;

&lt;p&gt;The best overview of how it works (with screenshots) is the help site: &lt;a href="https://dplcdwxautrmn.cloudfront.net/help/index.html" rel="noopener noreferrer"&gt;https://dplcdwxautrmn.cloudfront.net/help/index.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I feel the project is documented really well at this point, so I’ll stop here and just say please check out all the README.md files too (especially this one for a functionality overview: &lt;a href="https://github.com/indieTix-net/indietix/blob/main/infrastructure/FUNCTIONALITY.md" rel="noopener noreferrer"&gt;https://github.com/indieTix-net/indietix/blob/main/infrastructure/FUNCTIONALITY.md&lt;/a&gt;). I’d love feedback on the code, architecture or features if you all have time, and if anyone’s interested in helping build a Stripe or Lightspeed integration, even better!&lt;/p&gt;

</description>
      <category>free</category>
      <category>ticketing</category>
      <category>cinema</category>
      <category>entertainment</category>
    </item>
  </channel>
</rss>
