<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Asciinema on ditatompel Insights</title><link>https://insights.ditatompel.com/tags/asciinema/</link><description>Recent content in Asciinema on ditatompel Insights</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2022-2026 insights.ditatompel.com. All Rights Reserved.</copyright><lastBuildDate>Wed, 10 Apr 2024 19:29:54 +0700</lastBuildDate><atom:link href="https://insights.ditatompel.com/tags/asciinema/index.xml" rel="self" type="application/rss+xml"/><item><title>Rescue broken asciinema-server upgrade (PostgreSQL 12 => 14)</title><link>https://insights.ditatompel.com/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/</link><pubDate>Sat, 11 Mar 2023 08:52:39 +0700</pubDate><guid>https://insights.ditatompel.com/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/</guid><description>&lt;p>Today, I&amp;rsquo;m experiencing some problem with my recent self-hosted asciinema server upgrade. After following the upgrade process according to the &lt;a
 href="https://github.com/asciinema/asciinema-server/wiki/Installation-guide"
 
 target="_blank" rel="noopener noreferrer">asciinema-server documentation page on GitHub&lt;/a>, the &lt;code>phoenix&lt;/code> and &lt;code>postgresql&lt;/code> containers failed to run and kept restarting.&lt;/p></description></item></channel></rss>