Nostr notes by HomeLab

Narratarr: A Self-Hosted Audiobook Manager With a Built-In Player ...

2026-10-29T22:13:33Z

Narratarr: A Self-Hosted Audiobook Manager With a Built-In Player

I've always thought audiobooks deserved a little more attention in the self-hosting world. We've got some excellent applications for organizing movies and television shows, but audiobooks can be a different story. You might have a collection sitting on your NAS, yet finding new books and getting them properly organized often involves more manual work than it should.
Narratarr is a new self-hosted audiobook manager that follows the familiar approach of Sonarr and Radarr. It helps you find audiobooks, download them, and organize everything into a library. Unlike the usual *arr applications, though, Narratarr also includes its own audiobook player, so you don't necessarily need another application just to listen to what you've downloaded.
Finding Something Worth Listening To
I have a habit of browsing through media libraries even when I haven't decided what I want to watch or listen to. Half the fun is discovering something I'd completely forgotten about. Narratarr seems to understand that part of the experience, giving you a proper discovery interface rather than expecting you to arrive with a particular book already in mind.
The application connects to LibriVox and Old-Time Radio collections from the Internet Archive, providing access to thousands of freely available recordings. You can browse by genre or search for a particular title, with cover artwork and descriptions helping you figure out what you're looking at.
The Old-Time Radio collection is a fun inclusion. Those old radio dramas have a charm of their own, and having them mixed into an audiobook discovery interface makes browsing a little more interesting than another endless list of modern releases.
Narratarr also attempts to correct misspelled searches, which is useful when you can't quite remember how an author's name is spelled. That optional feature uses Apple's public search API, so it isn't entirely local, but the application works without enabling it.
Getting Books Into the Library
Those already running Sonarr or Radarr will recognize the general idea. Find something, add it to the download queue, and let the application handle organizing the files afterward.
Downloads from LibriVox and Old-Time Radio are fetched directly over HTTPS, without needing a paid service. Narratarr also supports Prowlarr for searching configured indexers and can pass Usenet downloads to SABnzbd.
Torrent downloads currently rely on Real-Debrid, which requires a paid account. That's worth knowing because Narratarr doesn't yet offer direct integration with qBittorrent or Transmission. Thankfully, none of that is necessary to use the free audiobook collections.
Finished books are arranged into author and title folders, with cover artwork and descriptive information saved alongside the audio. I can appreciate that because manually cleaning up audiobook downloads isn't exactly an enjoyable afternoon project.
Listening Without Another Application
Narratarr includes a browser-based audiobook player with chapter navigation and adjustable playback speed. It remembers where you stopped listening, which is especially important when a book takes considerably longer to finish than the average podcast episode.
There's a sleep timer as well, including an option to stop at the end of a chapter. That's a thoughtful touch for anyone who enjoys listening before bed and doesn't particularly want to wake up three hours further into the story.
The player handles books split across multiple MP3 files alongside M4B audiobooks, treating them as a continuous listening experience. It can also be accessed from a phone through the browser, without requiring a dedicated mobile application.
If you're already using Audiobookshelf, there's no need to abandon it. Narratarr can save books into a library Audiobookshelf recognizes and optionally trigger a scan after a download finishes.
Running Narratarr at Home
The developer provides a Docker Compose configuration with images for AMD64 and ARM64 machines. Everything runs in a single container, with separate mounts for application configuration and the audiobook library. The default web interface uses port 8484.
You can optionally enable password protection, although the documentation recommends keeping Narratarr on a trusted home network rather than exposing it directly to the internet.
Narratarr is a very new project, so I wouldn't be surprised to see a few rough edges as development continues. The GitHub repository is still relatively small, and there's not much independent feedback from people running it long-term.
Still, I think the combination of audiobook discovery and a built-in player makes sense. It's nice having the option to find a public-domain recording and start listening without setting up an entire collection of supporting services first. And for those of us already running an *arr stack, the additional integrations make it easy to see where Narratarr could fit.
You can find the Docker Compose setup and screenshots in the Narratarr GitHub repository. The README also explains how the different download sources work, which I'd recommend reading before connecting it to an existing media setup.
Explore more on Noted
Take a Poll | Play Trivia | Browse Giveaways

https://noted.lol/narratarr/

#audiobookmanager #narratarr #player #radio #downloads #something #books #radarr #sonarr #internetarchive

#rss #feeds #linksharing #qwibbit

RetroGemini: Self-Hosted Scrum Retrospectives At the State of ...

2026-10-21T19:41:15Z

RetroGemini: Self-Hosted Scrum Retrospectives

At the State of Geneva, we needed to keep candid team feedback on our own infrastructure. I decided to build an alternative, using AI to help with development.
The result is RetroGemini, an open source application for Scrum retrospectives and team health checks. Around 30 internal teams now use it. I am sharing it because other organizations may have the same constraint: useful collaboration tools, with the application and its data hosted internally.
A guided retrospective
A session follows a sequence: icebreaker, brainstorm, group, vote, discuss, review and close. Participants can write cards anonymously, group related ideas and vote on what to discuss. The facilitator has a timer and contextual guidance for each phase.
There are familiar templates such as Start/Stop/Continue, 4Ls and Sailboat, along with custom templates. Both the interface and retrospective templates support English and French. Each participant can choose an interface language independently, while the facilitator chooses the language of the board's template.
Follow-up actions can have assignees and carry over between sessions. Team health checks provide another way to track how a team is doing over time. Collaboration is synchronized in real time, so people can work on the same board from their own browsers.
Demo board with fictional data.
Try it with Docker
For a first trial, Docker is enough:
docker run --pull=always -d \
--name retrogemini \
-p 8080:8080 \
-v retro-data:/data \
jpfroud/retrogemini:latest
Open http://localhost:8080, create a team workspace with a recovery email, and start a retrospective. Use fictional data while you explore the workflow. The named volume keeps the SQLite database across container restarts.
For production, set a stable SESSION_TOKEN_SECRET, put the application behind an HTTPS reverse proxy and review the documented configuration. Self-hosting also means taking care of updates, backups and access to your server. The repository includes deployment documentation for Docker, Kubernetes and OpenShift.
Running it on an internal network
The core application does not require an external service at runtime. Its fonts, icons and other assets are self-hosted, and it can run on an isolated network. SQLite works for a single-container setup; PostgreSQL is another supported option.
SMTP and OpenAI-compatible AI features are optional and disabled unless configured. The AI features include card grouping and summaries. If you enable an integration, review where its data goes before using it with sensitive feedback. You can leave those integrations unconfigured and use the retrospective workflow without them.
Built with AI, used by real teams
I used AI to develop RetroGemini. The need behind it came from our working environment, and feedback from the teams using it helps shape the product. AI assistance during development does not mean participants need an AI account to run a retrospective.
The code is available under the Unlicense. You can find the source, installation instructions and configuration reference in the RetroGemini GitHub repository.
If your organization needs to keep retrospective feedback in-house, give it a try. I would be interested to hear what works for your teams and what you would change. If it is useful to you, a GitHub star is appreciated.

https://noted.lol/retrogemini/

#scrumretrospectives #retrogemini #docker #team #use #open #start #geneva #participants

#rss #feeds #linksharing #qwibbit

Your Homelab Doesn't Need to Run 24/7 There's something ...

2026-10-17T18:55:14Z

Your Homelab Doesn't Need to Run 24/7

There's something satisfying about having a rack full of servers running at home. The blinking lights, humming fans, and ability to spin up practically anything are part of what makes building a homelab enjoyable. But eventually, some of us discover that our impressive collection of hardware has become an expensive way to run a handful of Docker containers. Older enterprise servers are especially tempting because they're relatively inexpensive on the used market, often offering more memory and processing power than you'll ever need. Unfortunately, the purchase price is only part of the equation, and keeping everything running can quietly become one of your homelab's biggest expenses.
The Hidden Cost of Always-On Hardware
Consider a rack containing an older enterprise server, a NAS, and a network switch. Together, they might consume around 260 watts continuously, even when nobody is actively using most of the services. At that rate, the rack consumes approximately 187 kilowatt-hours over a 30-day month. With electricity priced at $0.20 per kilowatt-hour, that's roughly $37.44 monthly, or $456 annually. Additional workloads and cooling requirements can increase those expenses.
For comparison, a mini PC averaging 20 watts consumes just 14.4 kilowatt-hours monthly, costing approximately $2.88 at the same electricity rate. That's a substantial difference for someone whose essential services barely use the processing power of an aging rack server. Of course, a mini PC isn't a replacement for every enterprise workload, but it raises an interesting question about how much hardware genuinely needs to remain powered on.
Separate Essential Services From Your Lab
One of the simplest ways to reduce electricity consumption is to stop treating every server as essential infrastructure. Your DNS server probably needs to remain available, and home automation may depend on local services operating continuously. A password manager might also justify staying online. But what about those experimental virtual machines or the Kubernetes cluster you haven't touched in weeks? Many of us leave powerful hardware running simply because it's convenient, even when those machines aren't doing anything useful.
Separating everyday services from experimental workloads allows you to keep important applications running while shutting down unnecessary equipment. A modest computer running Proxmox or Linux with Docker can handle numerous lightweight services without requiring enterprise-grade hardware. Larger servers can remain available for demanding workloads, powered on only when needed. Wake-on-LAN can make this arrangement more convenient, provided your hardware supports it reliably.
A Mini PC Might Be All You Need
Modern mini PCs are remarkably capable, particularly for applications commonly found in homelabs. Services like Pi-hole, Uptime Kuma, and Vaultwarden generally require little processing power under normal household workloads. Even an inexpensive system can comfortably handle several Docker containers, provided it has adequate memory and storage.
That doesn't mean everyone should abandon rack servers. Enterprise hardware offers advantages, including greater expansion capabilities and remote management features. Someone experimenting with virtualization or running memory-intensive workloads may have legitimate reasons to maintain powerful equipment. However, if most of your homelab consists of applications waiting for occasional requests, you might be surprised by how little hardware is necessary.
Sometimes a Hybrid Homelab Makes Sense
Another possibility is moving selected services to an inexpensive VPS while keeping storage and experimental hardware at home. For example, a VPS could handle a public-facing reverse proxy while maintaining a private WireGuard connection to your local network. This can be useful when your home internet connection has limitations or you want certain services accessible during maintenance.
However, moving everything to a VPS isn't necessarily cheaper. Storage costs can become significant, particularly for media libraries, and remote hosting introduces another provider into your infrastructure. A hybrid approach works best when there's a clear reason for moving each service rather than simply trying to eliminate electricity consumption.
Measure Before Spending Money
Before replacing hardware, find out how much electricity your equipment actually uses. A plug-in electricity meter or compatible energy-monitoring smart plug provides real measurements instead of estimates based on specifications. If you're using Home Assistant, its Energy dashboard can help track electricity consumption from supported devices.
Pay particular attention to idle consumption because those costs accumulate even when nobody is using your applications. Calculate your annual electricity expenses and compare them against the cost of more efficient hardware. You might discover that upgrading makes financial sense, or that keeping your existing server is perfectly reasonable. Buying a $500 mini PC to save $20 annually probably isn't the financial victory you imagined.
Keep the Homelab, Rethink the Hardware
The appeal of self-hosting has never been exclusively about saving money. Some people genuinely enjoy experimenting with enterprise hardware, and that enjoyment is part of the hobby. A powerful server that helps you develop professional skills may also provide considerably more value than its electricity bill suggests.
But there's a difference between knowingly spending money on something you enjoy and leaving equipment running simply because you never considered turning it off. You don't have to give up your rack server or abandon the projects that made you interested in self-hosting.
Sometimes the smartest homelab upgrade isn't another server. It's realizing that the one you already own doesn't need to run all the time.

https://noted.lol/your-homelab-doesnt-need-to-run-24-7/

#run #services #need #hardware #mini #essential #might #hiddencost #docker #needmodern

#rss #feeds #linksharing #qwibbit

Noted 3.0: More Than a Redesign I’ve been working on Noted 3.0 ...

2026-10-15T21:33:39Z

Noted 3.0: More Than a Redesign

I’ve been working on Noted 3.0 for a while now, and it has turned into a much bigger update than I originally planned.
A lot of it started with small things that bothered me. Pages were getting harder to organize, older articles were getting buried, and I wanted certain parts of the site to have their own place instead of everything being mixed together.
So I started cleaning it up. It turned into a complete custom theme design.
The homepage has been reworked quite a bit. Recent posts are still there, but there are now better ways to get into the different parts of Noted without having to dig around.
One of the bigger additions is the new Get Started section. I took four articles that I think make a good starting point for someone new to self-hosting and turned them into a simple course. It starts with hardware, moves into the basics, then Docker and Portainer, and finishes with self-hosting Ghost. The articles need updating and I'll be working on that too.
Nothing is locked behind an account. It is just a cleaner way to work through the guides in order.
The Articles page also got a major overhaul. Instead of being a basic post archive, it now has live search and can actually search through the full Noted library, including older posts that were getting missed before.
There is also a completely new Polls section.
I’ve wanted Noted to feel a little more interactive for a while, without turning it into another social network. Polls seemed like a simple way to do that. I can throw up questions about self-hosting, Docker, operating systems, apps, or whatever else fits the site, and people can vote without having to write a full comment.
The polling system is built directly into Noted now, so the results update on the site as people vote.
I also added an Updates page.
This is where I can post smaller site updates, changelog-type notes, quick announcements, and things that don’t really need a full article. There is now a small lightning bolt in the header that links straight to it, especially useful on mobile.
I like having somewhere to post those little changes without making them compete with normal articles.
The Stats page is new too. Stats has the nerdy stuff like article counts, writing totals, publishing history, and popular topics.
Another new section is Themes.
I’ve been making more Ghost themes lately (including this one), so I wanted a proper place for them. Theme posts now have their own layout with version information, download links, release dates, and a changelog at the bottom.
There is also a small note on those posts explaining that AI is used during the design and development process. I think it is better to be upfront about that. I’m not a designer, but I have plenty of ideas I’ve wanted to see brought to life in Ghost. AI has helped me turn those ideas into actual themes, and the best part is they are all free.
A bunch of smaller things changed too.
Code blocks now have copy buttons. Author names link to their profiles. Comment counts show next to the reading time. GitHub repository links get cleaner cards. Sponsor posts stay out of the normal article feeds. The mobile experience on Noted has gotten a major update too. I cleaned up several layouts across the site, especially the homepage and Get Started page, so things feel less cramped and more consistent on smaller screens.
The search box was rebuilt too. The old one never really matched the site, and it was also missing older articles. The new search fits the theme better and searches everything.
There are still a few things I’ll probably tweak as I use it, but that is usually how Noted gets updated anyway.
Final Notes and Thoughts
The feature I’ve been most excited to add is Polls.
I’ve wanted a simple way for people to interact with Noted without having to leave a comment or create some long discussion. Sometimes I just want to ask a quick question like what Docker manager people are using, which operating system they prefer, or what self-hosted app they’ve been enjoying lately.
Now I can.
Polls are built directly into Noted, and the results are live. As people vote, you can head over to the Polls page and watch the numbers change.
That live part is probably what I like most about it. It makes the site feel a little more active instead of every article being something you simply read and move on from.
I’ve already got a bunch of poll ideas planned, and I think this is going to be one of the more fun parts of Noted going forward.
It’s simple on purpose. Pick an answer, vote, and see what everyone else thinks. It’s not bulletproof, but it’s fun, and I hope it adds just a little joy to your day.

https://noted.lol/noted-3-0/

Your Docker Backups Might Be Useless When You Need Them Most ...

2026-10-15T16:14:51Z

Your Docker Backups Might Be Useless When You Need Them Most

Backing up a self-hosted server sounds simple enough. Choose a backup application, point it at your Docker directories, configure a schedule, and let it run. As long as the dashboard shows a successful backup every night, everything should be fine.
But there's an uncomfortable question that many self-hosters never get around to answering: Could you actually restore everything if your server died tomorrow?
A successful backup doesn't necessarily mean your applications can be recovered. You might have every Docker Compose file safely stored away, only to discover that your database wasn't backed up correctly. Your files might be intact, but the environment variables needed to start an application are missing.
The problem isn't always the backup software. Sometimes it's how we've organized our self-hosted environments in the first place.
Backing Up Files Isn't the Same as Backing Up Applications
Docker makes deploying applications remarkably convenient, but it can create a false sense of simplicity when it comes to protecting their data.
A typical self-hosted application might have a Compose file stored in one directory, persistent data stored somewhere else, and a database running inside another container. Depending on how the application was deployed, some information might live inside Docker-managed volumes rather than easily accessible folders.
Simply copying the directory containing your Compose file won't necessarily preserve everything required to restore the service.
Even copying all persistent directories can introduce problems. Databases that are actively writing information may not produce consistent backups when their files are copied without coordination.
That's why a proper backup strategy needs to account for the entire application, including its persistent data and any required configuration.
The Problem With Having Too Many Backup Tools
There's no shortage of backup software available to self-hosters. Restic, BorgBackup, Kopia, Duplicati, and numerous management interfaces all provide ways to protect important files.
Yet choosing another backup application doesn't automatically solve the underlying problem.
Consider someone running twenty Docker containers across a dozen Compose projects. Each service has different requirements. Some need database dumps before backups begin, while others simply need a directory copied. Certain applications contain irreplaceable information, while others store temporary data that could easily be downloaded again.
A backup solution that treats every directory identically may waste considerable storage. Worse, a backup configuration that depends on manually adding every new project creates opportunities for important data to be overlooked.
For many home server owners, the missing feature isn't another backup format. It's a clear overview of which applications are protected and which ones aren't.
Organizing Your Docker Directories Can Make Recovery Easier
One practical improvement is keeping each application's configuration and persistent data organized under a predictable directory structure.
For example, a home server might use /docker/immich/ for its Immich deployment and /docker/vaultwarden/ for its password manager. Each directory could contain its Compose configuration and related application data, with appropriate handling for databases and secrets.
This doesn't mean every application must use bind mounts. Docker volumes have legitimate advantages, and certain applications are better suited to them. What matters is knowing exactly where important information lives and making sure your backup process includes it.
A consistent structure also makes individual application recovery considerably less intimidating.
Instead of restoring an entire server because one application failed, you can identify the affected project's configuration and recover the necessary data without disturbing unrelated services.
Your Database Deserves Special Attention
Databases are one of the easiest parts of a self-hosted setup to misunderstand.
Applications using PostgreSQL, MariaDB, or SQLite may continue accepting writes while a scheduled backup is running. Depending on the database and backup method, blindly copying live database files can produce an inconsistent snapshot.
The safer approach is to use a database-aware backup method, such as a supported database dump or a properly coordinated snapshot.
Some backup systems support scripts that execute before and after a backup. Those scripts can prepare an application for backup and restore normal operation afterward.
The exact process depends on the database and application. A method that works for one service may be inappropriate for another.
The important thing is understanding whether the data you're protecting can actually be recovered into a working application.
Don't Forget About Offsite Copies
Keeping backups on another drive inside the same server is useful, but it doesn't protect against every failure.
A serious hardware problem, theft, or accidental deletion could affect both the original data and its local backup.
The familiar 3-2-1 backup strategy remains a useful starting point: three copies of important data, stored across two types of storage, with one copy maintained offsite.
For a homelab, that might mean keeping the original application data, a local backup repository, and another protected copy on a remote server or cloud storage provider.
Encryption is particularly important when transferring personal files or application databases to storage you don't directly control.
It's also worth considering whether a compromised server could delete its own backups. Versioned snapshots, restricted credentials, and storage protections can make recovery more resilient.
The Restore Test Most People Skip
Perhaps the most valuable backup practice is also the least exciting: actually testing recovery.
Choose a noncritical application and restore it into an isolated environment. Recreate its configuration, recover the data, and verify that it behaves as expected.
Don't assume that seeing files inside a backup archive means the application will start successfully.
You may discover that an environment variable was excluded, a database dump is incompatible with the application version, or an unexpected permission prevents the container from accessing restored files.
Finding those problems during a planned test is inconvenient. Discovering them after a drive failure can be devastating.
It's also worth documenting the recovery process somewhere outside the server itself. Instructions stored exclusively on the machine you're trying to recover aren't especially helpful when that machine becomes unavailable.
A Backup Is Only as Good as Your Ability to Restore It
Self-hosting offers something valuable: control over the services and information we depend on.
But that control also comes with responsibility.
You don't necessarily need an expensive enterprise backup platform or a complicated collection of scripts to protect your homelab. A straightforward system that consistently captures the right data and makes restoration understandable can be far more valuable than an elaborate setup nobody knows how to recover.
The next time your backup dashboard reports another successful run, consider doing something different.
Pick an application and try restoring it.
You might discover that your backups are working perfectly. Or you might uncover a problem that's been quietly waiting for the worst possible moment.
[trivia:15]

https://noted.lol/docker-backups-restore-self-hosted-apps/

Is Cloudflare Tunnel Actually Secure for Self-Hosting? I've ...

2026-10-15T09:10:47Z

Is Cloudflare Tunnel Actually Secure for Self-Hosting?

I've used several methods for accessing my self-hosted applications remotely over the years, but I've grown particularly fond of Cloudflare Tunnel. It's convenient, doesn't require opening ports on my router, and makes it relatively easy to access applications through my own domains.
But I've seen people question how secure Cloudflare Tunnel actually is, especially when it comes to exposing applications running on a home server. It's a fair question, considering how much personal data some of us keep on our homelabs.
So, is Cloudflare Tunnel really safe to use?
What Does Cloudflare Tunnel Actually Protect?
One of the biggest advantages of Cloudflare Tunnel is that it doesn't require inbound connections to your home network. Instead, a small application called cloudflared establishes an outbound connection to Cloudflare, allowing visitors to reach your services without directly connecting to your server's public IP address.
This eliminates the need for traditional router port forwarding and helps keep your server's public IP address hidden from visitors accessing those services.
That's a pretty significant security benefit, particularly for anyone who doesn't want to deal with exposing individual ports on their home network.
However, there's an important detail that I think some self-hosters overlook.
Just because you're using Cloudflare Tunnel doesn't mean your application is private.
If you publish something like a Docker dashboard through a public hostname, anyone who knows that address may be able to reach its login page. Cloudflare Tunnel doesn't automatically require visitors to authenticate before connecting to your application.
That's where additional protection becomes important.
Cloudflare Access Adds Another Layer
Cloudflare offers a service called Cloudflare Access that allows you to restrict access to applications before visitors can reach their login pages.
For example, you could configure Access so that only approved email addresses can connect to your self-hosted dashboard. Anyone else would be stopped before reaching the application itself.
I think this is particularly useful for administrative interfaces that have no reason to be publicly accessible.
There is one thing to consider, though. Applications that rely on their own desktop or mobile clients may not work properly behind a browser-based Cloudflare Access login. You should test synchronization and API functionality before enabling additional authentication.
What Cloudflare Tunnel Doesn't Protect You From
While Cloudflare Tunnel reduces certain risks, it doesn't eliminate the need to secure the applications running behind it.
If an application contains a vulnerability that can be exploited through its publicly accessible interface, using a tunnel doesn't necessarily prevent someone from exploiting it. Weak passwords can still be a problem, and improperly configured services can expose information you never intended to make public.
There's also the connection between cloudflared and your application to consider. If your tunnel forwards requests over HTTP, that final connection isn't independently encrypted. This is generally less concerning when everything runs on the same trusted machine, but it's worth considering when traffic travels across other network devices.
Cloudflare also sits between visitors and your application, which means you're trusting another company to handle that traffic. That's a trade-off worth understanding if privacy is one of your primary reasons for self-hosting.
Is Cloudflare Tunnel Worth Using?
For my own homelab, I think Cloudflare Tunnel is a great solution for accessing applications remotely. I appreciate not having to expose ports on my router, and managing access through Cloudflare has made things more convenient.
But I wouldn't treat it as a replacement for properly securing the applications themselves. I still need to keep my software updated and make sure I'm not exposing administrative interfaces unnecessarily.
If you're using Cloudflare Tunnel, I'd encourage you to review your published application routes and consider which services actually need public access. For anything particularly sensitive, Cloudflare Access or a private VPN connection might be a better approach.
Cloudflare Tunnel can be a valuable part of a secure self-hosting setup. You just need to understand what it's responsible for protecting.
Cloudflare Tunnel isn't the only option available, either. If you'd rather manage your own tunneling infrastructure, I've also covered Pangolin, a self-hosted reverse proxy with built-in authentication that uses WireGuard tunnels. It's worth looking into if you want another approach to remote access.
Pangolin: Easy Self-Hosted Tunneled Reverse Proxy with Built-in Auth via VPS
The all new tunneled reverse proxy Pangolin is here. And it’s super easy to setup!
NotedJeremy
I've also added a poll at the end of this article featuring a handful of the more popular reverse proxy options. So far, Caddy and Nginx Proxy Manager seem to be the favorites among Noted readers. If you haven't voted yet, scroll down and let us know which one you're using. I'm curious to see how the results change as more votes come in.
You can learn more about how tunnels work in the official Cloudflare documentation.
[poll:1]

https://noted.lol/is-cloudflare-tunnel-secure/