Docker Wts Build

io.github.artemdruzhininad-starPublished by GitHub account artemdruzhininad-starv0.1.2Updated Oct 24, 2026

Schedule Docker builds via Windows Task Scheduler — survives VS Code terminal timeouts

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Schedules Docker Compose builds through Windows Task Scheduler so long builds keep running after VS Code terminal timeouts.

What you can do
  • Schedule Docker builds as Windows Task Scheduler tasks so they outlive editor terminal sessions.
  • Point it at a project directory and choose the Compose file, custom services, task name prefix and timeout.
  • Write build logs to a configurable logs directory.
  • Clean up old tasks based on a maximum task age in days.
When to use it
Useful on Windows when Docker Compose builds are long enough to be cut off by VS Code terminal timeouts and you want them to run detached and be logged. Less relevant if you build on Linux, macOS, or in CI.
Requirements
Runs locally as a PyPI package over stdio on Windows, using Windows Task Scheduler. Requires Docker with Compose and a project directory set via DWTB_PROJECT_DIR; optional settings include DWTB_COMPOSE_FILE, DWTB_CUSTOM_SERVICES, DWTB_LOGS_DIR, DWTB_MAX_TASK_AGE_DAYS, DWTB_TASK_PREFIX and DWTB_TASK_TIMEOUT_MS.
Before you install
It creates and deletes Windows scheduled tasks and runs Docker builds on your machine, so builds execute real commands and consume resources. Cleanup removes tasks older than the configured age. No authentication is declared; anyone who can run the server can schedule builds in the configured project.

Installation

In SourceWeft

  1. Open Docker Wts Build in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.