The topic I built my entire developer workflow around these Docker containers, and I’m not… is currently the subject of lively discussion — readers and analysts are keeping a close eye on developments.
This is taking place in a dynamic environment: companies’ decisions and competitors’ reactions can quickly change the picture.
Docker started as a convenient way for me to test apps without cluttering my system, but it gradually became the foundation of my entire developer workflow. Instead of installing every database, service, dashboard, and utility directly on my machine, I now run most of them inside containers that I can launch, update, and remove in minutes.
The result is a cleaner setup, fewer dependency conflicts, and a development environment that is much easier to implement across projects.
Gitea is one of the most important containers in my developer workflow because it gives me a private, lightweight home for all my code. I still use GitHub for public projects and collaboration, but not every experiment, unfinished idea, or client project belongs there.
With Gitea running in Docker, I can host my own Git repositories, create branches, track issues, review commits, and manage projects without depending on a third-party platform.
The biggest advantage for me is control. My repositories stay on my hardware, and I decide how they are backed up, accessed, and organized. I can also spin up Gitea alongside the rest of my development stack using Docker Compose, making the setup easy to reproduce when I move to another machine or server.
Dockge is the container I use to keep the rest of my Docker setup manageable. As my workflow grew from a handful of services to multiple Compose stacks, editing YAML files manually and jumping between terminal commands started to feel tedious.
Dockge gives me a clean visual interface to create, edit, start, stop, restart, and monitor my Docker Compose projects from one place.
My stack files remain readable and portable, so I can still open them manually, move them to another machine, or manage them from the terminal whenever I need to.
Dockge may not be the most exciting container in my setup, but it is one of the most practical. It serves as the control panel for my Compose stacks, which power my developer workflow and make the entire environment easier to maintain.
Activepieces is part of my developer workflow because it helps me automate the repetitive tasks that often sit between coding, testing, and deployment.
I can connect apps, APIs, webhooks, and databases through visual workflows instead of writing a separate script for every small task. for example, I can use Activepieces to send a notification when a deployment finishes, create a task when a new issue is reported, move data between services, or trigger a workflow whenever an API receives a webhook.
Running it as a Docker container also fits neatly into the rest of my setup. I control where it runs, how its data is stored, and which services it can access.
Syncthing keeps important project files synchronized across my devices without forcing me to rely on a traditional cloud storage service. I use it for configuration files, scripts, documentation, local assets, and other development resources I may need on multiple machines.
Once I add a folder, Syncthing automatically watches for changes and updates the other connected devices in the background.
What I like most is that the data moves directly between my own devices. There is no central cloud drive storing a copy of everything, and I remain in control of which folders are shared and where they are stored. Running Syncthing in Docker also keeps the setup isolated and easy to maintain alongside the rest of my self-hosted stack.
I still use Git for source code and version history, but Syncthing fills a different role. It handles the supporting files that do not always belong in a repository.
Nginx Proxy Manager gives me a clean and practical way to access all my self-hosted services. Instead of remembering a different IP address and port number for every container, I can assign each service a simple domain or subdomain.
That means I can open tools like Gitea, Dockge, Activepieces, or Uptime Kuma using easy-to-remember addresses rather than typing 192.168.x.x:3000 every time.
It also helps me add HTTPS to my services with far less effort. I can request and renew certificates, force secure connections, and apply access controls without rebuilding my entire networking setup.
Uptime Kuma gives me a simple way to monitor the services I depend on every day. Once I started running tools like Gitea, Dockge, Activepieces, Outline, Mealie, Syncthing, and Nginx Proxy Manager through Docker, I needed something that could tell me when one of them stopped responding.
Uptime Kuma fills that role without adding much complexity. I use it to monitor websites, internal services, ports, and APIs from a single dashboard. At a glance, I can see whether everything is online, how quickly each service is responding, and whether there have been any recent interruptions.
The notification system is useful, too. I can configure alerts through services like Telegram which I already use. So I know when a container goes down or when a response time suddenly becomes unusually high.
It does not directly help me write code, but it protects the environment around my work.
Building my developer workflow around Docker was not about running containers simply because I could. Each one solves a specific problem that previously required another subscription, manual setup, or repetitive task.
Dockge keeps my Compose stacks manageable, and Activepieces handles the automation I do not want to repeat. Syncthing gives me control over my files, while Uptime Kuma ties everything together by watching the entire setup and alerting me when something goes wrong.
This stack is flexible, private, and easy to rebuild, which is exactly why I am not going back to my old developer workflow.
Along with these, I am also toying with self-hosted local LLMs to boost my dev workflow.
Docker Desktop is a one-click-install application for your Mac, Linux, or Windows environment that lets you build, share, and run containerized applications and microservices. It provides a straightforward GUI (Graphical User Interface) that lets you manage your containers, applications, and images directly from your machine.
Docker Desktop reduces the time spent on complex setups so you can focus on writing code. It takes care of port mappings, file system concerns, and other default settings, and is regularly updated with bug fixes and security updates.