https://github.com/rigeldev/deno-deployctl
Deno image with the Deno Deploy deployctl command line installed.
https://github.com/rigeldev/deno-deployctl
deno deno-deploy
Last synced: 17 days ago
JSON representation
Deno image with the Deno Deploy deployctl command line installed.
- Host: GitHub
- URL: https://github.com/rigeldev/deno-deployctl
- Owner: rigeldev
- Created: 2024-10-29T09:19:54.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2024-10-30T05:55:37.000Z (6 months ago)
- Last Synced: 2025-02-11T17:57:53.558Z (2 months ago)
- Topics: deno, deno-deploy
- Language: Dockerfile
- Homepage:
- Size: 4.88 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# deno-deployctl
> docker pull rigeldev/deno-deployctl:latest
Docker image for deploying applications to [Deno Deploy](https://deno.com/deploy).
Uses [denoland/deno](https://hub.docker.com/r/denoland/deno) as base image and installs the [deployctl](https://github.com/denoland/deployctl).
## Tags
For tagging I'm using the following pattern `deno-version`-`deployctl-version`.
[Available tags](https://hub.docker.com/r/rigeldev/deno-deployctl/tags)
## Status
I'm manually doing the updates and versioning for now since I'm just doing some initial tests with Deno Deploy.
When my usage becomes more stable / when I'm more invested into [Deno Deploy](https://deno.com/deploy) it will make sense to
automate following the versioning of the base image and the deployctl tool.