Worker
A worker connects a Docker host to the application and performs the operations you request.
Learn about workers →worqer.appOpening application…
worqer.app documentation
Learn how to connect a Docker host and take an application from a Git repository to a running deployment.
Two concepts to get started
Deployment
A deployment is the complete configuration and running result of one project on a selected worker.
Learn about deployments →Architecture
worqer.app separates the place where a developer configures an application from the Docker host where it runs. The panel provides one interface for projects, workers and deployments; each worker connects an authorized Docker host and executes the requested deployment there.
Inputs
Developers add a Git repository, choose a branch and define Build, Environment and access settings.
Control panel
The panel organizes projects, selects the destination worker and exposes deployment operations in one interface.
Worker hosts
The selected worker builds and runs the application with Docker on its connected machine.
Results
Containers, status, logs, ports and optional public URLs appear as the deployment result.
Why the separation matters
The panel can manage multiple Docker hosts without moving their runtime into the web application. The worker stays close to Docker, and every project explicitly selects where it should run.
Problems it solves
Different Docker hosts
Connect multiple machines as named workers and choose where each project should run without changing the project workflow.
Repeated manual deployments
Keep the repository, branch, build mode, variables and worker together so a deployment can be repeated consistently.
Compose and Dockerfile differences
Use a clear build selector and display only the settings relevant to the chosen mode.
Scattered runtime operations
Deploy, restart, inspect logs, execute configured commands, stop and remove applications from one deployments view.
Temporary public access
Expose the intended service through ngrok, see its URL beside the deployment and close the tunnel when it is no longer needed.
Unclear deployment failures
Show deployment results and actionable worker or ngrok errors near the affected application.
Workers
A worker represents a Docker host where your applications can be cloned, built and run. Add at least one worker before creating a deployment.
Connect a worker
You can create a worker on a new Docker host or use one that is already running. In both cases, the worker must appear online and be available to your user before assigning it to a project.
Create a worker
Run the worker image on the Docker host, preserve its data directory and claim it using the token printed in its logs.
Create a worker →Use an existing worker
Claim an unassigned worker with its token, or select an available worker that is already connected to the workspace.
Use an existing worker →Create a worker
Run a worker on your own computer for local development or on a Debian VPS for an always-on deployment host. Both options support the Python and Go worker images.
Choose a worker image
Python worker · :py
The stable Python implementation. Choose this tag when you want the reference runtime and broad compatibility.
cjarn/docker-panel-lite-worker:pyGo worker · :go
The compiled Go implementation. Choose this tag for a lightweight worker with lower runtime overhead.
cjarn/docker-panel-lite-worker:goClaim either worker
- Wait for the worker container to start.
- Copy the claim token shown by the script or
docker logs --tail 100 worqer-worker. - Open Workers in worqer.app.
- Paste the token into Worker token and select Claim.
- Confirm that the worker appears online, then select it in Project Settings → Environment.
Keep each worker identity separate
The mounted /app/data folder preserves the worker identity and claim token. Never share the same data folder between your PC and VPS workers.
Use an existing worker
Choose the case that matches the current state of the worker:
| Worker state | What to do |
|---|---|
| Running but not claimed | Read its token with docker logs --tail 100 worqer-worker, enter it in Workers and select Claim. |
| Already visible to your user | No token is required. Open Project Settings → Environment and select it as the default worker. |
| Owned by another user | Ask the owner to share the worker with your user or make it available to the workspace. |
| Offline | Start the worker on its Docker host and wait until it reports an online state. |
Test worker token
This token is provided only for the test worker and must not be reused for production infrastructure.
nYunaGwdMrEUAl7j02A8KeunUsJzFk2PAssign it to a project
Open Project Settings → Environment and select the worker. Deploy, sync and runtime operations for that project will use the selected Docker host.
Worker troubleshooting
| Symptom | What to check |
|---|---|
| Worker appears offline | Confirm its container is running, review its logs and verify network access. |
| Worker does not appear | Confirm the claim token and refresh the Workers page. |
| Docker operation fails | Verify Docker is available on the host and the worker has the required access. |
| Project runs on the wrong host | Review the selected worker in the project Environment tab. |
Deployments
A deployment is everything required to turn a project into a running application. It combines the source, build instructions, environment, destination worker, running containers and access options in one place.
What a deployment contains
Identity
Project alias and description used to recognize the application.
Git source
Repository URL, branch and credential when the repository is private.
Build
Docker Compose or Dockerfile mode, file paths, service and port configuration.
Environment
The variables the application needs while it is running.
Worker
The Docker host selected to build and run the application.
Runtime
Containers, images, current status and exposed ports.
Access
Visibility, permitted users, local addresses and optional public URLs.
History
Deployment results and errors that help verify or troubleshoot a release.
Git source
Register an existing local project or clone a repository. Configure its URL, branch and an authorized credential when needed. After a successful Register or Clone action, the project panel closes and the project appears in the list.
Build and environment
The Build tab defines how the application is created. The Environment tab contains runtime variables and the worker selector.
Docker Compose
Use this for applications described by a Compose file. Select the file and configure the service and port used to reach the application.
Dockerfile
Use this to build and run one service. Select the Dockerfile, build context and port mappings for that container.
Only the selected mode applies
Project Settings shows the fields related to Docker Compose or Dockerfile so it is clear what will run.
Public URLs and ngrok
A deployment can remain private or expose a temporary public URL through ngrok. In the project Domain tab, enter the ngrok token first and then enable Public. You can generate a token from the discreet link next to the token field.
- A token belongs to its ngrok account; using a token from another account uses that account.
- Account limits and available domains depend on the ngrok plan.
- For Compose projects, select the service and internal port that should receive traffic.
- Close Public URL stops the tunnel even when the application container is not running.
- Close URLs that are no longer needed before opening more sessions.
ngrok errors
If ngrok rejects a session, review the message shown by the deployment. It may indicate account, billing, agent-limit, domain or upstream-port problems.
Available operations and icons
The icons below are the same ones used in the application. Primary actions remain visible on each row; actions marked More appear inside the three-dot menu. Some operations only appear when the worker and container are in an eligible state.
Projects
Project operations act on the Git source and the complete application configuration.
RefreshPrimary
Pulls the latest source and refreshes project information from the selected worker.
SettingsPrimary
Opens Git, Build, Environment, Domain and Access configuration.
DeployPrimary
Builds and starts the project using its selected Compose or Dockerfile mode.
MorePrimary
Opens the compact menu that contains the less frequent project operations.
View Compose / DockerfileMore
Reads and displays the build file detected on the selected worker.
Deployment eventsMore
Shows progress, results and errors from project operations.
Open / refresh public URLsMore
Creates or regenerates the configured ngrok URLs.
Close public URLsMore
Stops the public tunnels created for the project.
Stop projectMore
Stops the Compose stack or Dockerfile-managed service without deleting the project.
Deployments
Deployment operations act on an individual Docker container and its runtime.
Public URLPrimary
Creates or regenerates public access for a running service.
RestartPrimary
Restarts the running container without rebuilding the project source.
MorePrimary
Opens the compact menu with state-dependent container operations.
StartMore
Starts a stopped container.
Run commandMore
Runs the selected saved command inside an eligible running container.
View logsMore
Opens the runtime output for the selected container.
StopMore
Stops a running container while preserving it.
DeleteMore
Removes the managed container; use it only when the runtime is no longer needed.
Deploy is different from Restart
Use Deploy after changing source, Build or Environment. Use Restart when the current deployed version only needs to restart at runtime.
Deployment troubleshooting
| Symptom | What to check |
|---|---|
| Repository cannot be cloned | URL, branch and selected Git credential. |
| Compose or Dockerfile cannot be read | File path relative to the repository and worker availability. |
| Build fails | Deployment result, build file and required environment variables. |
| Application is not reachable | Container status, listening address and configured internal port. |
| Public URL fails | The exact ngrok error, account limits, domain availability and target service. |