If Docker teaches humility, Nextcloud teaches patience.
By the time Nextcloud entered the picture, most of the infrastructure already worked:
public HTTPS
reverse proxying
dynamic DNS
service subdomains
Jellyfin
Needle
Immich
Everything appeared stable.
Then Nextcloud calmly announced:
“Access through untrusted domain.”
Which, to be fair, was entirely reasonable.
The application was protecting itself correctly.
Still, this marked the beginning of another fascinating realization:
Modern self-hosted systems increasingly expect a canonical identity.
One URL.
One secure endpoint.
One consistent origin.
That raised an important philosophical dilemma.
At home, using:
homeserver.local:8080
felt practical.
But externally:
was clearly the proper public endpoint.
The temptation to maintain separate internal and external URLs appeared immediately.
And technically, it was possible.
But eventually the cleaner architecture revealed itself:
Use the public HTTPS URLs everywhere.
Always.
Even internally.
That single decision simplified:
synchronization
certificates
redirects
authentication
mobile apps
future deployment logic
It also subtly transformed the philosophy of the entire platform.
The homeserver stopped being:
“a collection of local services.”
And became:
“a coherent personal cloud ecosystem.”
That distinction matters more than it sounds.
Because once every service lives behind:
proper HTTPS
stable DNS
canonical URLs
reverse proxy routing
…they stop feeling like experiments.
They start feeling like products.
And perhaps that is the strangest realization of all.
Needle began as a personal music player.
Somewhere along the way, it accidentally became the catalyst for re-learning:
networking
infrastructure
reverse proxies
public internet architecture
service design
self-hosting philosophy
and operational thinking.
Not because of ambition.
But because every solved problem naturally exposed the next layer underneath.
And maybe that is the real beauty — and danger — of personal projects.
They rarely stay small.