The latest articles on DEV Community by Markus Cadonau (@cadonau). https://dev.to/cadonau https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F5523%2F8995a1c6-435f-48e2-95a3-e52b23fe07a3.png https://dev.to/cadonau en Markus Cadonau Thu, 03 Nov 2022 07:54:30 +0000 https://dev.to/cadonau/avif-images-in-ios-160s-safari-1kkc https://dev.to/cadonau/avif-images-in-ios-160s-safari-1kkc <p>I noticed that some of my (<a href="https://www.cadonau.net/photos/">album cover</a>) photos don’t display in Safari on the newly released iOS 16. Xe Iaso had already <a href="https://xeiaso.net/blog/avif-help-requested">posted about problems</a>, as well. To me, it looks like the exact same issue: AVIF images encoded with <a href="https://github.com/Kagami/go-avif"><code>go-avif</code></a> appear broken.<br><br> As there is a <a href="https://bugs.webkit.org/show_bug.cgi?id=245097">WebKit bug report</a> now, I’m wondering whether the encoding is actually the problem, as the images have also been showing fine in Firefox and Chrome.</p> <h2> Update </h2> <p>The issue is <a href="https://bugs.webkit.org/show_bug.cgi?id=244103">fixed</a> in iOS <a href="https://webkit.org/blog/13399/webkit-features-in-safari-16-1/">16.1’s Safari</a>:</p> <blockquote> <p>Fixed some AVIF images not rendering because of their container format.</p> </blockquote> <p>(Changing the “major brand” from <code>mif1</code> to <code>avif</code> in the <a href="https://en.wikipedia.org/wiki/ISO_base_media_file_format#File_type_box">file type box</a> of the images would have also worked.)</p> webdev Markus Cadonau Mon, 18 Oct 2021 06:20:03 +0000 https://dev.to/cadonau/deploybot-configuration-with-git-lfs-55i5 https://dev.to/cadonau/deploybot-configuration-with-git-lfs-55i5 <p>I recently started using Git LFS for image and video files in an existing repository. Migrating the repository to Git LFS would be another Odyssean story.</p> <p>However, since I’m using DeployBot to deploy the repository to a web server, I also had to make sure <em>it</em> would handle the files properly, i.e. the actual image files, not the text pointers would be transferred to the host.<br><br> An answer to DeployBot’s “<a href="https://support.deploybot.com/article/63-common-questions-about-build-tools">common questions about build tools</a>” says:</p> <blockquote> <p>Unfortunately, we do not yet support LFS by default. But it is possible to use Git LFS right now by using build tools. Inside the container, you are free to install the LFS plugin and set things up yourself. You could also use a command to install the LFS distribution.</p> </blockquote> <p>It took me a while to figure out how to do it but I think it now works for my scenario. It’s probably not ideal; I will try to update this post, if I change my configuration. Let me go through what I’ve tried:</p> <h2> First Attempt </h2> <p>I started <a href="https://support.deploybot.com/article/61-setting-up-and-using-build-tools">configuring my own container</a> based on the existing Ubuntu 18.04 one with the</p> <p><em>Build commands</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>apt install git-lfs git lfs install --system </code></pre> </div> <p>to install Git LFS and set its Git hooks up.<br><br> That alone was not sufficient. Git LFS was set up — so I kept the setting — but text pointers were being deployed.</p> <h2> Second Attempt </h2> <p>In the deployment server settings, by adding the following commands to the <a href="https://support.deploybot.com/article/61-setting-up-and-using-build-tools">Build Tools</a> section</p> <p><em>Compile, compress, or minimize your code</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>cd /source/ git lfs pull </code></pre> </div> <p>I tried to make Git LFS replace the text pointers with the media files. Yet, text pointers were still being deployed.</p> <h2> Third Attempt </h2> <p>Realizing that the files weren’t being pulled from my original (Github) repository, I modified</p> <p><em>Compile, compress, or minimize your code</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>cd /source/ git remote set-url origin %REPO_URL% git lfs pull </code></pre> </div> <p>so that the ”origin” remote was set to my repository, not to some intermediate one by DeployBot.<br><br> While this worked, DeployBot viewed all LFS files as different and always deployed all of them again.</p> <h2> Fourth Attempt </h2> <p>Once again, I modified</p> <p><em>Compile, compress, or minimize your code</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>cd /source/ git checkout -b deploy %PREVIOUS_COMMIT% git remote set-url origin %REPO_URL% git pull origin %BRANCH% </code></pre> </div> <p>to only pull the files from my repository that were modified since the last deployed commit.<br><br> This worked until I had to roll back for the first time since making these configuration modifications.</p> <h2> Fifth Attempt </h2> <p>So I first made sure that a rollback was not happening by using a conditional statement in</p> <p><em>Compile, compress, or minimize your code</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>cd /source/ if [ %ROLLBACK?% != 1 ]; then git checkout -b deploy %PREVIOUS_COMMIT% git remote set-url origin %REPO_URL% git pull origin %BRANCH% fi </code></pre> </div> <h2> Sixth Attempt (November 2021 Update) </h2> <p>After some renamed/moved LFS files had — once again — not been properly pulled and deployed, I realized that the “deploy” branch could not be created on DeployBot instances where it already existed (from a recent deployment) resulting in a failed checkout.<br><br> By making the option uppercase I think I finally managed to configure DeployBot with Git LFS to my satisfaction. For completeness sake, I’m including all parts of my current configuration, again:</p> <p><em>Build commands</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>apt install git-lfs git lfs install --system </code></pre> </div> <p><em>Compile, compress, or minimize your code</em></p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>cd /source/ if [ %ROLLBACK?% != 1 ]; then git checkout -B deploy %PREVIOUS_COMMIT% git remote set-url origin %REPO_URL% git pull origin %BRANCH% fi </code></pre> </div> git lfs deployment