Deployarr v5 Launched: Is it an Embarrassment? BS?

Sorry, that was a clickbait title (you will find the reason later in this article).

As you may have noticed, I have not published an article in over 3 months. This is the longest break I have taken from writing. But it wasn't really a break.

I have been busy publishing videos on my YouTube channel and working on developing Deployarr v5.

Deployarr v5 is the biggest update since the original launch in September 2023. It was a complete rewrite from scratch and I touched over 9000 lines of code and spent nearly 150 hours on it.

I think that the result is visible with the improved UX, fluidity, and features. Let's take a deeper look at Deployarr v5 and also touch on other topics, including migrating from v4 to v5.

Intro Video

The easiest and shortest way to know how Deployarr works and take a look at its features is with this 20 min intro video.

What's New in Deployarr v5

This article is a bit late, Deployarr v5.0.1 is already out, but it is a bugfix release. Here is a detailed changelog:

• NEW: Deployarr logo and icon.
• NEW: Local mode for installing apps for local access only (no reverse proxy). This should now remove the Traefik requirement and allow multi-server setups.
• NEW: Traefik Exposure Modes. Simple - all apps behind Traefik accessible internally and externally. Advanced - control over exposing apps internally, externally, or both.
• NEW: By default Traefik will use file providers to expose apps via reverse proxy. Previously this was done using Docker labels. Some apps (e.g. Traefik, OAuth, and Authelia), will continue to use labels.
• NEW: Deployarr Dashboard - New Homepage based dashboard that auto-populates as you install new apps. It works but will evolve over time.
• NEW: Recommended order of steps for various setups.
• NEW: License changes. There are now 3 license types: Basic, Plus, and Pro. Basic allows local-only installs.
• NEW: Deployarr pin reset feature.
• NEW: All apps are now exposed to Docker host using ports. Deployarr will suggest ports during installation.
• NEW: Deployarr will now call Cloudflare API to check the validity of the DNS API token for Traefik.
• NEW: Included v4 to v5 migration instructions.
• ENCHANCEMENT: Descriptive error messages when requirements are not met for a specific step.
• ENCHANCEMENT: Signficant improvement in speed/responsiveness.
• ENHANCEMENT: Menu reorganized based on past feedback.
• REMOVED: Traefik v2 to v3 migration.
• REMOVED: Auto-Traefik to Deployarr migration.
• REMOVED: Account registration directly from the script. Not needed anymore, as all previous "Basic" features are now free for anyone.
• OTHERS: Eleventy-million minor changes (over 9000 lines of code rewritten).

Getting Started

Detailed Video Guide

With the launch of Deployarr v5, I also published a detailed 1.5 hour long video guide showing pretty much all the steps in order. It should answer most of the questions. Check it out.

Migrating from v4 to v5

Migrating from v4 to v5 can be a challenge. With the complete rewrite, to support future development, Deployarr switched from Docker labels to Docker file provider as the way of exposing apps (except Traefik, Authelia, and Google OAuth) via Traefik.

Now it is possible to dynamically change the exposure of apps, authentication method, etc. without having to restart the service.

This change, however, means that those of you who are on v4 will have older Docker compose files that are still on Docker labels. Manually changing everything over can be tedious. The following video shows the recommended method to migrate from v4 to v5.

What's Planned for Deployarr v6?

There will be several sub-releases before the work on version 6 starts. In Deployarr v5, I plan to add several more apps based on all requests I got on Youtube and Discord.

This is not written in stone, but here are some ideas for Deployarr v6:

• Cloudflared to expose apps without port-forwarding
• Support for SMB and NFS mounts (in addition to Rclone)
• Authentik
• Nginx Proxy Manager / Caddy
• Teacher mode for additional explanations along the way

If you have other requests, feel free to leave a comment below. Synology support will be targetted probably in version 7. Or, it could be sooner. As I mentioned, the list is fluid and it depends on what is easier to accomplish.

Supporting Open-Source

Thanks to the overwhelming support from the community (except a few negative nancies online), I have been able to fund the YouTube videos, pay myself some for the time and effort, and donate to many of the open-source projects.

The homelab apps we love and use require a huge amount of effort to develop, maintain, and support. Deployarr v5 launch was quite successful and I was able to contribute a big chunk to the several projects.

Deployarr Contributes to Several Projects (over $425 contributed)

Deployarr will continue to support many of these projects in an ongoing basis.

Nay-sayers

There was some push back from some folk online that called Deployarr "an embarrassment" and I am "piggy-backing" on well-known names (Traefik and Arr) for my own personal interest.

Here is a Reddit thread (there are others). At least one person (u/MrBuckwheet) deleted his comments after saying I was "exploiting" people and Deployarr was "BS" for not being clear about paid license (while also posting a screenshot of the license types from Deployarr, which showed free/paid options).

I take all feedback seriously. Here is my response to many concerns/false claims found online:

1. No one is forced to pay for Deployarr. Everything that Deployarr does is explained in my guides. I do not hide anything. In fact, I built deployarr to be compatible with my guides and vice versa. In the videos I clearly say, "if you want to learn then use my guides instead".
2. No registration or payment is required to setup docker environment, do checks for traefik suitability, etc. which complement my written guides and saves a lot of time and mistakes. License types are clearly explained everywhere, including Deployarr GitHub and Deployarr page.
3. I am proud of the amount of time, effort, and money (yes, some articles cost over $300) I put into writing my guides and videos to teach. If you are able to find something more detailed and coherent than my guides and now YouTube videos on Docker, and especially Traefik, please share.
4. Now to go along with my guides I started making videos and spent over $3000 so far in editing costs alone as I have no time to edit, while making <$200 in ads. Once again, please find me guides or videos that cover from from the beginning to the end, as I do on my Docker Playlist and Traefik playlist. Deployarr is what funds these.
5. A big chunk of Deployarr money goes towards supporting open-source projects (see above). It would be safe to say that vast majority of the selfhosters do not contribute.
6. As for the name, I picked names to imply what the tool does. When Auto-Traefik was launched it automated Traefik setup and so Auto-Traefik. Then it grew to what it is now, and I wanted to call it something to imply what it does, which is to automate setup of your Docker based homelab, including Arr apps and so Deployarr. It does not just pull some random compose files and start them for you. It sets up a whole ecosystem, except configuring the individual apps.
7. If you have been blogging for 15 years on homelab topics, you would know the time and effort it takes. Never charged anything for 14 of those years. Traffic and ad revenue dropped nearly 99% from the peak and I had to find ways to sustain and continue doing what I love. If my aim was to sell Deployarr, there is no reason for me to put out detailed guides and videos.
8. I might link to my free guides, but I have never promoted Deployarr in any of the public forums except my own youtube channel and website. I know fully well that it may not be for everyone.

As I have always said, if Deployarr does not work for you, just reach out to me on Discord and I will refund your money. Teaching has always been my passion and I have been doing this for 15 years.

Closing Thoughts

But some of the feedback I received did remind me of something important.

So I want to reiterate (as I do in all my guides and videos on Deployarr) that Deployarr is not meant to be black box and it is not a replacement for learning. Users have always had access to all files and folders Deployarr created.

Teacher mode, although it was already planned, will address some negative (disrespectful/judgmental) sentiment about automated tools. I don't plan on changing the name from Deployarr though.

Everyone prefers different ways of learning. Some have the time and interest. And some not and may prefer something that makes their life easier. I made Deployarr to help both and nudge folks who were afraid take a step into the homelabbing world because everything looked so intimidating/overwhelming. Even my own guides can be intimidatingly/overwhelmingly long.

And if I find someone who is not willing to put in the time and effort to learn, I have flat out told them on my Discord that I can refund and they should read my guides.

At the end of the day, homelabbing is supposed to be a fun learning experience. That is what I am trying to do with Deployarr (and 8 years back with AtoMiC Toolkit). If it is not your cup of tea, no problem. The good thing is there are so many options.

Go Geek Army!