<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ashley Tsuma on Medium]]></title>
        <description><![CDATA[Stories by Ashley Tsuma on Medium]]></description>
        <link>https://medium.com/@tsumaashley?source=rss-9210d31f9645------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*UKCwt9dgljltXDhq</url>
            <title>Stories by Ashley Tsuma on Medium</title>
            <link>https://medium.com/@tsumaashley?source=rss-9210d31f9645------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:51:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tsumaashley/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Rebase vs Merge: The Git Concept That Finally Clicked.]]></title>
            <link>https://medium.com/@tsumaashley/rebase-vs-merge-the-git-concept-that-finally-clicked-d4045615ad51?source=rss-9210d31f9645------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4045615ad51</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Ashley Tsuma]]></dc:creator>
            <pubDate>Sat, 01 Aug 2026 06:20:29 GMT</pubDate>
            <atom:updated>2026-08-01T06:20:29.891Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing nobody tells you about contributing to open source is how quickly you’re expected to pick up new concepts.</p><p>One day you’re making your first contribution, and the next you’re told to “rebase your branch” or “just merge the latest changes.” I remember staring at those words thinking, “I have no idea what the difference is.” 😅</p><p>During my internship, I encountered both merge and rebase while working on contributions. The project moved fast, and while everyone was incredibly helpful, it wasn’t exactly beginner-friendly. That pushed me to stop memorising Git commands and actually understand what they do.</p><p>Looking back, I don’t think the hardest part was learning Git. It was learning how to ask the right questions and being okay with not understanding everything immediately. Every confusing command eventually became another piece of the puzzle.</p><p>Let’s get cracking. 👏</p><p><strong>Merge</strong>, in simple terms:</p><p>Think of merge as combining two branches while keeping the full history of both.</p><p>- It preserves your branch history.</p><p>- It creates a merge commit.</p><p>- It’s great when you want to keep the complete story of how work happened, especially on shared branches.</p><p>What about <strong>rebase</strong>?</p><p>Rebase takes your work and reapplies it on top of the latest version of another branch, making it look like you started from the most recent changes all along.</p><p>The result? A cleaner, more linear commit history.</p><p>Rebase is commonly used to update your feature branch before opening or updating a pull/merge request, making the history easier to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mYOEPMoKBNQLPWWaiLsMDQ.png" /><figcaption>Here is a simple diagram to help you understand better :)</figcaption></figure><p><strong><em>So… which one should you use?</em></strong></p><p>- Use merge when preserving the complete history of a shared branch is important.</p><p>- Use rebase when you want a cleaner commit history on your own feature branch before sharing your work.</p><p>Neither is “better” than the other they simply solve different problems.</p><p>The biggest lesson I learned wasn’t how to run “git merge” or “git rebase”. It was understanding why my team chose one over the other in different situations. Once that clicked, Git became a lot less intimidating.</p><p>Till next time. ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4045615ad51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Testing Fastlane on Debian to Writing Contributor Documentation]]></title>
            <link>https://medium.com/@tsumaashley/from-testing-fastlane-on-debian-to-writing-contributor-documentation-4821e096e6bf?source=rss-9210d31f9645------2</link>
            <guid isPermaLink="false">https://medium.com/p/4821e096e6bf</guid>
            <category><![CDATA[froid]]></category>
            <category><![CDATA[fastlane]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[debian]]></category>
            <dc:creator><![CDATA[Ashley Tsuma]]></dc:creator>
            <pubDate>Wed, 18 Feb 2026 13:56:15 GMT</pubDate>
            <atom:updated>2026-02-23T08:08:53.774Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first set out to test <strong>Fastlane</strong> on Debian, I assumed it would be simple: install the tools, run a lane, and watch the automation unfold. Instead, the experience turned into a deeper exploration of reproducibility, environment setup, and the reality of open-source contribution where learning happens through iteration, troubleshooting, and documentation.</p><h3>Starting Out : First Steps with Fastlane on Debian</h3><p>My initial goal was to test the Fastlane workflow alongside the F-Droid plugin. I began by installing Fastlane and preparing my environment, planning to use an APK already available in my repository.</p><p>That plan quickly changed.</p><p>I discovered that Fastlane’s nightly build workflow expects <strong>source code rather than prebuilt binaries</strong>. This became my first major “aha” moment:</p><p>Automation relies on reproducibility, and reproducibility starts with source.</p><p>Instead of simply hosting APK files, I needed a full Android project that could be built automatically.</p><h3>Switching to Flicky : Building Instead of Hosting</h3><p>To move forward, I chose <strong>Flicky </strong>, an open-source project already available on F-Droid, and cloned its repository as my test project.</p><p>This gave me:</p><p>· Proper Gradle configuration</p><p>· Android project structure</p><p>· Build scripts compatible with automation workflows</p><p>At this stage, the process shifted from experimentation into real pipeline setup. I wasn’t just testing commands I was learning how automated build systems actually work.</p><h3>Wrestling with Paths, Environment Variables, and Keystores</h3><p>The next challenges were less about code and more about environment configuration.</p><p>Debian repeatedly exposed issues with incorrect paths environment variables were referencing the wrong user directory . Fixing this taught me how sensitive automation pipelines are to precise configuration.</p><p>Then came signing builds.</p><p>Fastlane required a .jks keystore file, which I didn’t initially have. Learning to generate one using keytool, fill in certificate details, and connect it to my workflow through environment variables was a major milestone.</p><p>Each small fix built a deeper understanding of how build pipelines actually function behind the scenes.</p><h3>Adjusting the Fastfile :Learning to Read Errors</h3><p>Another learning moment came when I encountered an invalid credential type error. After digging into the plugin requirements, I realized the parameter names needed to match exactly for example:</p><p>· github_personal_access_token instead of github_token</p><p>This reinforced an important lesson:</p><p>Automation tools are precise by design and error messages are often the best documentation you have.</p><p>Updating my Fastfile accordingly helped me better understand how Fastlane plugins consume configuration.</p><h3>Transitioning from Debian to Ubuntu</h3><p>After stabilizing the workflow on Debian, I moved to Ubuntu to verify reproducibility across environments.</p><p>This step wasn’t just about changing systems it was about validating the process itself.</p><p>On Ubuntu, I:</p><p>· Reinstalled dependencies from scratch</p><p>· Repeated the setup process</p><p>· Compared behavior between operating systems</p><p>· Identified which issues were configuration-specific versus environment-specific</p><p>Some problems disappeared entirely, highlighting how system differences can influence development workflows.</p><p>This phase strengthened my contributor mindset:</p><p>Documentation must work beyond your own machine.</p><h3>From Testing to Documentation-Writing the Contributor Wiki</h3><p>With the workflow tested, my focus shifted toward creating contributor documentation.</p><p>This required a different perspective. Instead of asking:</p><p>“Does this work for me?”</p><p>I had to ask myself:</p><p>“Can another contributor follow this successfully without confusion?”</p><p>Writing the wiki involved:</p><p>· Documenting exact command sequences</p><p>· Clarifying directory structures (especially Fastlane metadata paths)</p><p>· Including validation steps to confirm metadata detection</p><p>· Anticipating common errors and troubleshooting scenarios</p><p>I realized that good documentation is both technical and empathetic guiding someone through the process while reducing friction.</p><p>also here is the link to the wiki if you’re intrested in testing the plugin on ubuntu: <a href="https://github.com/AshStellare/Fastlane-plugin/wiki/Installation-Guide">https://github.com/AshStellare/Fastlane-plugin/wiki/Installation-Guide</a></p><h3>What This Process Taught Me</h3><p>This journey has been less about getting everything right immediately and more about learning through iteration.</p><p>Key lessons:</p><p>Automation depends on reproducible source workflows<br> Environment setup is as important as code itself<br> Testing across systems improves documentation quality<br> Troubleshooting is not failure it’s part of understanding the system deeply</p><p>Most importantly, contributing to open-source documentation changed how I think about development. It’s not just about building solutions; it’s about enabling others to build alongside you.</p><h3>Closing Thought</h3><p>Testing Fastlane on Debian, validating it on Ubuntu, and transforming that experience into contributor documentation showed me that automation isn’t magic. It’s careful setup, precise configuration, and persistence.</p><p>Each obstacle became a stepping stone and each step brought me closer to understanding how collaborative open-source workflows truly operate.</p><p>#OpenSource #FDroid</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4821e096e6bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience Deploying an F-Droid Repository with Fastlane]]></title>
            <link>https://medium.com/@tsumaashley/my-experience-deploying-an-f-droid-repository-with-fastlane-b3826260f24e?source=rss-9210d31f9645------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3826260f24e</guid>
            <dc:creator><![CDATA[Ashley Tsuma]]></dc:creator>
            <pubDate>Wed, 11 Feb 2026 17:47:53 GMT</pubDate>
            <atom:updated>2026-02-11T17:47:53.654Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>My Experience Deploying an F-Droid Repository with Fastlane</strong></p><p>One of the tasks assigned was to explore how to automate the creation and deployment of an F-Droid repository using Fastlane, rclone, and Backblaze B2 cloud storage. This process helped me understand not only deployment automation but also how Android app distribution infrastructure works behind the scenes.</p><p>This blog documents what I learned, the challenges I faced, and how I solved them.</p><p><strong>Understanding the Goal</strong></p><p>The objective was to:</p><p>Create an F-Droid repository<br> Automate repository management using Fastlane<br> Deploy the repo to Backblaze B2 cloud storage<br> Make APKs publicly accessible.</p><p>Unlike Google Play, F-Droid repositories allow developers to distribute open-source Android applications independently.</p><p><strong>Tools Used</strong></p><p>The workflow involved several tools working together:</p><ul><li><strong>F-Droid Server Tools-</strong>generates repository metadata and indexes.</li><li><strong>Fastlane-</strong>automation tool for defining repeatable deployment workflows.</li><li><strong>rclone</strong> -cloud storage synchronization tool.</li><li><strong>Backblaze B2</strong> -object storage used to host the repository.</li></ul><p>Each tool plays a specific role:</p><ul><li>Fastlane defines commands (called lanes).</li><li>F-Droid builds repository metadata.</li><li>rclone uploads files to cloud storage.</li></ul><p><strong>Setting Up the Repository</strong></p><p>First, I created the repository structure using:</p><p>fdroid init</p><p>This generated:</p><ul><li>repository folders</li><li>configuration files</li><li>signing setup.</li></ul><p>I then defined Fastlane lanes inside the Fastfile:</p><p>`lane :create_repo do</p><p>sh(“fdroid init”)</p><p>end</p><p>lane :update_repo do</p><p>sh(“fdroid update &amp;&amp; fdroid update -c”)</p><p>end</p><p>lane :deploy_repo do</p><p>sh(“fdroid deploy -v”)</p><p>end`</p><p>This allowed me to automate all repo operations using simple commands.</p><p><strong>Configuring Backblaze B2 Deployment</strong></p><p>Instead of using a global rclone configuration, the project required a custom configuration file:</p><p>backblaze.conf</p><p>Example:</p><p>[backblaze-config]</p><p>type = b2</p><p>account = &lt;KeyID&gt;</p><p>key = &lt;ApplicationKey&gt;</p><p>This configuration was referenced inside config.yml:</p><p>rclone: true</p><p>awsbucket: fastlaneplugintestbucket</p><p>rclone_config: backblaze-config</p><p>path_to_custom_rclone_config: /home/user/fastlane-directory/backblaze.conf</p><p><strong>Challenge I Encountered</strong></p><p>One major issue was that deployment failed because rclone attempted to load the default configuration file instead of the custom one.</p><p>The documentation used:</p><p>/root/fastlane-directory/backblaze.conf</p><p>However, my environment was not running as root.</p><p>Changing the path to:</p><p>/home/myusername/fastlane-directory/backblaze.conf</p><p>And resolved the issue.</p><p>This taught me an important lesson: Always verify absolute file paths when working with automated tools.</p><p><strong>Deploying the Repository</strong></p><p>After setup, deployment was simple:</p><p>bundle exec fastlane deploy_repo</p><p>This command then:</p><ol><li>Generated repository metadata.</li><li>Signed the repository.</li><li>Synced files to Backblaze using rclone.</li></ol><p><strong>Issue:</strong></p><p><strong>Title:</strong> fdroid_nightly_github fails with FileNotFoundError when no Android project is present</p><p><strong>Description:</strong> <br> I followed the instructions on the F‑Droid Fastlane Plugin wiki to set up a nightly repo on GitHub. My setup has:</p><ul><li>fastlane/repo/ containing APKs and metadata</li><li>fastlane/Fastfile with the lanes defined</li><li>a keystore (sample.jks) in the project root</li></ul><p>When I run:</p><p>`bundle exec fastlane fdroid_nightly_github`</p><p>I got this error:</p><p>FileNotFoundError: [Errno 2] No such file or directory: ‘/home/ashley/fastlane-directory’</p><p>The stack trace points to fdroidserver/nightly.py trying to create androiddir. The documentation doesn’t explain that an Android project is required in android/ for nightly builds. Without source code, the command always fails.</p><p><strong>Steps to reproduce:</strong></p><ol><li>Create a fastlane/repo with an APK and metadata.</li><li>Initialize Git and connect to GitHub.</li><li>Run` bundle exec fastlane fdroid_nightly_github`</li></ol><p><strong>Expected behavior:</strong> <br> Either the plugin should handle publishing an existing repo without requiring an Android project, or the documentation should clearly state that nightly builds require an Android project in android/.</p><p><strong>Actual behavior:</strong> <br> The command crashes with a FileNotFoundError because no android/ project exists.</p><p><strong>Suggestion:</strong> <br> Clarify in the documentation that:</p><ul><li>deploy_repo is for publishing an existing repo (APKs already built).</li><li>fdroid_nightly_github is for nightly rebuilds and requires an Android project in android/.</li></ul><p>That’s all for now until next time :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3826260f24e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A continuation on docker:]]></title>
            <link>https://medium.com/@tsumaashley/a-continuation-on-docker-a1ea657f060e?source=rss-9210d31f9645------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1ea657f060e</guid>
            <dc:creator><![CDATA[Ashley Tsuma]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 11:37:46 GMT</pubDate>
            <atom:updated>2026-02-02T11:37:46.086Z</atom:updated>
            <content:encoded><![CDATA[<p>A continuation on docker:</p><p>The Docker executable image documentation explains how to run F-Droid server tools inside a Docker container instead of installing them directly on the host system. This approach packages all required dependencies into a pre-configured environment, making it platform-independent and easier for beginners. While the documentation provides command examples, it assumes prior Docker knowledge and lacks beginner-oriented explanations, which can make it difficult for new users to follow.</p><p>When Attempting to use the official Docker image <em>docker-executable-fdroidserver</em> to initialize a repository it failed because the container does not include a usable fdroid executable.</p><p>This is a documentation gap. A<strong> working alternative</strong> is to install F-Droid server tools natively, or use a community Docker image.Which i proceded to do!</p><p>I then successfully created an F-Droid repository using fdroidserver. Then added a test APK to the repository to validate the indexing and update process using fdroidserver. <em>cd ~/fdroid-repo/my-repo</em></p><p><em>cp ~/Downloads/org.fdroid.fdroid_1019050.apk repo/</em></p><p>To add an app, an existing APK is copied into the repo directory. Running <em>fdroid</em> update –c generates metadata and indexes the APK. F-Droid does not build the app at this stage; it manages and distributes signed APKs.</p><p>This APK was downloaded from the official F-Droid catalog for testing purposes only, to demonstrate repository setup.</p><p>That was it for docker till the next blog :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1ea657f060e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Prepared an environment for F-Droid repository creation by installing Docker, setting up a local…]]></title>
            <link>https://medium.com/@tsumaashley/i-prepared-an-environment-for-f-droid-repository-creation-by-installing-docker-setting-up-a-local-1f1eb8508183?source=rss-9210d31f9645------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f1eb8508183</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[f-droid]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Ashley Tsuma]]></dc:creator>
            <pubDate>Sat, 24 Jan 2026 14:31:33 GMT</pubDate>
            <atom:updated>2026-01-24T14:31:33.090Z</atom:updated>
            <content:encoded><![CDATA[<p>I Prepared an environment for F-Droid repository creation by installing Docker, setting up a local workspace, and preparing a test APK.</p><p>Steps:</p><p>1. Installed Docker to simplify running F-Droid server tools in a containerized environment.</p><p>2. Created a local working directory to hold repository configuration, APKs, and generated metadata. This is the fdroid-repo/</p><p>└── repo/</p><p>3. Prepared a test APK to validate repository creation and indexing.</p><p>I then proceeded to create a beginner F-Droid repository using the Docker-based F-Droid server tools. The process involved setting up a repository directory, defining basic configuration in a config file, adding APK files, and using F-Droid tools to generate repository metadata and an index. Docker simplified the setup by handling dependencies, making it suitable for beginners.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f1eb8508183" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Studied F-Droid server tools, explored installation methods (Linux, source, Docker), reviewed…]]></title>
            <link>https://medium.com/@tsumaashley/studied-f-droid-server-tools-explored-installation-methods-linux-source-docker-reviewed-fa3ce733f86c?source=rss-9210d31f9645------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa3ce733f86c</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Ashley Tsuma]]></dc:creator>
            <pubDate>Tue, 20 Jan 2026 08:16:23 GMT</pubDate>
            <atom:updated>2026-01-20T08:16:23.342Z</atom:updated>
            <content:encoded><![CDATA[<p>Studied F-Droid server tools, explored installation methods (Linux, source, Docker), reviewed repository deployment steps, and analyzed documentation gaps and improvement areas.</p><p>An F-Droid repository is created by configuring a workspace, adding APKs or source applications, generating metadata and an index using F-Droid server tools, and serving the resulting files over HTTP.</p><p>Steps : First understand F-Droid concepts, then explore installation options, I chose Docker, then prepare configuration and files, and finally create the repository.</p><p>Takeaway: The F-Droid documentation presents multiple ways to install server and repository tools. The Debian/Ubuntu method demonstrates how the tools are traditionally installed on Linux systems and highlights required dependencies. Installing the latest code provides access to the newest features but is aimed at developers and contributors due to its complexity. The Docker-based approach bundles all dependencies into a single container, making it the most beginner-friendly and reliable option for creating and managing an F-Droid repository.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa3ce733f86c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>