Latest posts tagged with #taskfile on Bluesky
Akkoma002
部署完成
终于完成了...
当初手动部署Akkoma踩过的坑，现在自动化部署还要再踩一遍 (
使用Taskfile.yml实现`task install`自动完成Akkoma Docker部署以及DNS、S3配置等等
以及
`task reset`：一键自毁
`task create-admin`：创建Admin
`task clean`：清理编译产物（和`task reset`区分开来）
docs.akkoma.dev/stable/installation/dock...
#akkoma #taskfile #docker
Welcome to Misskey
配合Taskfile、Cloudflare DNS API、Caddy和Docker
已经能实现批量生产`白板`misskey实例了
自动添加DNS记录
自动配置default.yml docker.env compose.yml
自动配置域名证书
自动构建/使用现有镜像
自动执行数据库初始化等等......
有NixOS 的神韵了感觉...
#taskfile #misskey
I been looking at #taskfile and this is complex. 🤔 The command runner has so many abilities. And verbose too. 🫠
I don't think I'll use for myself, but I can see utility for shared tasks.
For me #justfile is enough. Not too complex. Has a #makefile syntax. And NOT #yaml. 😅
taskfile.dev/usage/
Dealing with #Ansible & #docker compose on #synology systems and an alternative #taskfile option
Let's dive in: buff.ly/xoSjQ1A
The alternative with taskfile: buff.ly/bMcd7SG
Using #Taskfile to deal with docker-compose vs docker compose on different systems
buff.ly/bMcd7SG
#Taskfile
* Modern alternative to Makefiles with YAML syntax (so way easier to debug)
* I store frequently used command sequences in one place
Examples:
* Installing uv, required Python version, creating env, and installing packages
* Custom sequence for updating Airflow versions quickly
Another beautiful feature of #task is to include other taskfiles. Especially to have them OS specific where desired.
Just include the desired #taskfile. Use `{{OS}}` to make it dynamic, allowing variables or tasks to be OS dependent. Useful for developing on Mac and running on Linux (or pipelines)
Depending on the pipeline system you're using, you might need to specify the commands to be executed yourself (jenkins, gitlab, ...)
Hang on... You just created that beautiful #taskfile to make your life easier... Why not make your pipeline easier, by just executing your tasks...
You are expanding your #taskfile and realise that there a couple of tasks with dependencies on a build process.
Though you don't want to rebuild it, if nothing changed. #Task got you covered!
Using sources and generates to monitor the source files and if the generated file exists.
You need to run a command for some sub-directories of your project... Doing this with make, you'd need to manually put your logic in to jump back up a dir.
No thinking required with #task. Just add an entry to the array, it always starts from the #taskfile location.
You have this beautiful #Taskfile helping you out. Though some systems use exec1 for a certain task, while the other use exec2.
A concrete example could be 'docker-compose' vs 'docker compose'.
Here is a way of working with that.
❯ task a -n
task: [a] docker compose --help
