Practical overview
When it fits
Use it when you manage a Docker host and want GitHub Actions to handle image building, deployment and scheduled strategy-file updates for a Dockerized Freqtrade instance.
Who it is for
- People operating a Docker host who want repository commits to trigger deployment of a Freqtrade instance.
- Users who want scheduled synchronization of strategy, blacklist and pairlist files into the deployment workflow.
Documented uses
- Build and push a Docker image after repository commits.
- Deploy the configured production.yml to a remote Docker host.
- Pull strategy-related files on a schedule and trigger deployment when they change.
- Optionally receive deployment messages in a Telegram chat.
Requirements & limits
- A Docker host and Docker Hub account are required for the documented deployment.
- The workflow depends on GitHub secrets for registry credentials, host access and scheduled updates.
- Telegram notifications are optional and require a bot token and chat identifier.
- A different strategy-file source requires modifications to the scheduled workflow and credentials.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up remote Docker deployment
Prepare the repository to build and deploy its Docker image to a remote Docker host.
Before you start
- A Docker host
- A Docker Hub account
- A fork of the repository
- GitHub secrets for Docker Hub username and password, Docker host, SSH private and public keys, and a GitHub personal access token
Steps
Fork the repository.
Add the required Docker Hub, host, SSH-key and GitHub-token values as GitHub secrets.
If needed, edit production.yml so its image name matches your Docker Hub username.
Commit a change to the repository to trigger the documented build, image push and deployment workflow.
Expected outcome
A repository commit triggers a Docker image build and push, followed by deployment of production.yml to the configured host.
Guide limitations
- The Docker host and credentials must be supplied by the user.
- The README notes that the image name in production.yml may need changing.
Enable scheduled strategy-file updates
Configure the scheduled workflow to retrieve strategy-related files from its documented upstream and deploy changes.
Before you start
- A fork of the repository
- A GitHub personal access token configured as the GH_PAT secret
- The remote deployment secrets required by the build-and-deploy workflow
Steps
Configure GH_PAT as a GitHub secret.
Use the repository's scheduled update workflow, which checks the configured upstream for strategies, blacklists and pairlist files.
When files change, the workflow commits them to the repository, triggering the deployment workflow.
Expected outcome
Changes to the configured strategy-related files can trigger a new deployment; Telegram messages are sent if the Telegram secrets are configured.
Guide limitations
- The README specifies NostalgiaForInfinity as the upstream source.
- The README says the schedule is set to run every minute but GitHub Actions runs it about every five minutes.
- Using a different upstream requires changes to the workflow and credentials.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- p-zombie/freqtrade · Official homepage title · retained in its source language