#justfile — Public Fediverse posts

Global #justfile: run recipes from anywhere

https://eshlox.net/global-justfile

Has anyone ever used `just` instead of `make` as a task runner for a project? If so, how did it work for you? Any feedback?

https://just.systems/man/en/

I have some nontrivial cargo command invocations that need to support parameterization, so I'm considering adding a task runner to the project. Just wondering, should I stick with `make`, or try something new? 🤔

#just #make #justfile #makefile #taskrunner

Has anyone ever used `just` instead of `make` as a task runner for a project? If so, how did it work for you? Any feedback?

https://just.systems/man/en/

I have some nontrivial cargo command invocations that need to support parameterization, so I'm considering adding a task runner to the project. Just wondering, should I stick with `make`, or try something new? 🤔

#just #make #justfile #makefile #taskrunner

Has anyone ever used `just` instead of `make` as a task runner for a project? If so, how did it work for you? Any feedback?

https://just.systems/man/en/

I have some nontrivial cargo command invocations that need to support parameterization, so I'm considering adding a task runner to the project. Just wondering, should I stick with `make`, or try something new? 🤔

#just #make #justfile #makefile #taskrunner

Has anyone ever used `just` instead of `make` as a task runner for a project? If so, how did it work for you? Any feedback?

https://just.systems/man/en/

I have some nontrivial cargo command invocations that need to support parameterization, so I'm considering adding a task runner to the project. Just wondering, should I stick with `make`, or try something new? 🤔

#just #make #justfile #makefile #taskrunner

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. 😅

https://taskfile.dev/usage/

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. 😅

https://taskfile.dev/usage/

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. 😅

https://taskfile.dev/usage/

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. 😅

https://taskfile.dev/usage/

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. 😅

https://taskfile.dev/usage/

I received an recommendation for https://github.com/casey/just 💡 #justfile

I received an recommendation for https://github.com/casey/just 💡 #justfile

I received an recommendation for https://github.com/casey/just 💡 #justfile

I received an recommendation for https://github.com/casey/just 💡 #justfile

I received an recommendation for https://github.com/casey/just 💡 #justfile

The @tailscale folks have some excellent YT videos on setting up self-hosted servers on Digital Ocean using Terraform, Ansible, and of course, Tailscale. I just got my first Droplet running.

Part 1 - Getting started with cloud-init: https://youtu.be/e-X5FJwrkaA?si=t3iLP-k9B4SmDAMp
Part 2 - Terraform: https://youtu.be/PEoMmZOj6Cg?si=2IwHCw4HuIa71YFZ
Part 3 - Ansible: https://youtu.be/k5Xgt31yK2U?si=28MPbwmiIOB-18nv

#selfhosting #Tailscale #privacy #indiweb #terraform #ansible #justfile

The @tailscale folks have some excellent YT videos on setting up self-hosted servers on Digital Ocean using Terraform, Ansible, and of course, Tailscale. I just got my first Droplet running.

Part 1 - Getting started with cloud-init: https://youtu.be/e-X5FJwrkaA?si=t3iLP-k9B4SmDAMp
Part 2 - Terraform: https://youtu.be/PEoMmZOj6Cg?si=2IwHCw4HuIa71YFZ
Part 3 - Ansible: https://youtu.be/k5Xgt31yK2U?si=28MPbwmiIOB-18nv

#selfhosting #Tailscale #privacy #indiweb #terraform #ansible #justfile

The @tailscale folks have some excellent YT videos on setting up self-hosted servers on Digital Ocean using Terraform, Ansible, and of course, Tailscale. I just got my first Droplet running.

Part 1 - Getting started with cloud-init: https://youtu.be/e-X5FJwrkaA?si=t3iLP-k9B4SmDAMp
Part 2 - Terraform: https://youtu.be/PEoMmZOj6Cg?si=2IwHCw4HuIa71YFZ
Part 3 - Ansible: https://youtu.be/k5Xgt31yK2U?si=28MPbwmiIOB-18nv

#selfhosting #Tailscale #privacy #indiweb #terraform #ansible #justfile

The @tailscale folks have some excellent YT videos on setting up self-hosted servers on Digital Ocean using Terraform, Ansible, and of course, Tailscale. I just got my first Droplet running.

Part 1 - Getting started with cloud-init: https://youtu.be/e-X5FJwrkaA?si=t3iLP-k9B4SmDAMp
Part 2 - Terraform: https://youtu.be/PEoMmZOj6Cg?si=2IwHCw4HuIa71YFZ
Part 3 - Ansible: https://youtu.be/k5Xgt31yK2U?si=28MPbwmiIOB-18nv

#selfhosting #Tailscale #privacy #indiweb #terraform #ansible #justfile

The @tailscale folks have some excellent YT videos on setting up self-hosted servers on Digital Ocean using Terraform, Ansible, and of course, Tailscale. I just got my first Droplet running.

Part 1 - Getting started with cloud-init: https://youtu.be/e-X5FJwrkaA?si=t3iLP-k9B4SmDAMp
Part 2 - Terraform: https://youtu.be/PEoMmZOj6Cg?si=2IwHCw4HuIa71YFZ
Part 3 - Ansible: https://youtu.be/k5Xgt31yK2U?si=28MPbwmiIOB-18nv

#selfhosting #Tailscale #privacy #indiweb #terraform #ansible #justfile

Ok, this seems _pretty ok_. Each project's `justfile` will have a little boilerplate of 2 imports and a `fetch` recipe.

My default justfile can be grabbed with `just fetch` if users want it. The second import is mostly for me and my local filesystem setup.

That should solve for my local dev, make it relatively easy for other devs to get my default `justfile`, _and_ not repeat the same recipes in every project.

I think. We’ll see! 😅

https://github.com/adamghill/dotfiles/

#Python #justfile

Ok, this seems _pretty ok_. Each project's `justfile` will have a little boilerplate of 2 imports and a `fetch` recipe.

My default justfile can be grabbed with `just fetch` if users want it. The second import is mostly for me and my local filesystem setup.

That should solve for my local dev, make it relatively easy for other devs to get my default `justfile`, _and_ not repeat the same recipes in every project.

I think. We’ll see! 😅

https://github.com/adamghill/dotfiles/

#Python #justfile

Ok, this seems _pretty ok_. Each project's `justfile` will have a little boilerplate of 2 imports and a `fetch` recipe.

My default justfile can be grabbed with `just fetch` if users want it. The second import is mostly for me and my local filesystem setup.

That should solve for my local dev, make it relatively easy for other devs to get my default `justfile`, _and_ not repeat the same recipes in every project.

I think. We’ll see! 😅

https://github.com/adamghill/dotfiles/

#Python #justfile

Ok, this seems _pretty ok_. Each project's `justfile` will have a little boilerplate of 2 imports and a `fetch` recipe.

My default justfile can be grabbed with `just fetch` if users want it. The second import is mostly for me and my local filesystem setup.

That should solve for my local dev, make it relatively easy for other devs to get my default `justfile`, _and_ not repeat the same recipes in every project.

I think. We’ll see! 😅

https://github.com/adamghill/dotfiles/

#Python #justfile

Ok, this seems _pretty ok_. Each project's `justfile` will have a little boilerplate of 2 imports and a `fetch` recipe.

My default justfile can be grabbed with `just fetch` if users want it. The second import is mostly for me and my local filesystem setup.

That should solve for my local dev, make it relatively easy for other devs to get my default `justfile`, _and_ not repeat the same recipes in every project.

I think. We’ll see! 😅

https://github.com/adamghill/dotfiles/

#Python #justfile

Sharing so it's easier for me to remember: #justfile recipes can take splat arguments.

test *args:
  pytest tests {{ args }}

Means I can do

just test -xk Links

and that'll expand to

pytest tests -xk Links

Sharing so it's easier for me to remember: #justfile recipes can take splat arguments.

test *args:
  pytest tests {{ args }}

Means I can do

just test -xk Links

and that'll expand to

pytest tests -xk Links

Sharing so it's easier for me to remember: #justfile recipes can take splat arguments.

test *args:
  pytest tests {{ args }}

Means I can do

just test -xk Links

and that'll expand to

pytest tests -xk Links

Sharing so it's easier for me to remember: #justfile recipes can take splat arguments.

test *args:
  pytest tests {{ args }}

Means I can do

just test -xk Links

and that'll expand to

pytest tests -xk Links

Sharing so it's easier for me to remember: #justfile recipes can take splat arguments.

test *args:
  pytest tests {{ args }}

Means I can do

just test -xk Links

and that'll expand to

pytest tests -xk Links

@Larvitz

Well, you could make that into a just recipe and then make it "just update". 😅

#justfile
https://github.com/casey/just

Baked into #UniveralBlue projects as "ujust update".

@Larvitz

Well, you could make that into a just recipe and then make it "just update". 😅

#justfile
https://github.com/casey/just

Baked into #UniveralBlue projects as "ujust update".

Unreasonably pleased by a tiny tweak to #plaintextaccounting scripts. I keep most of them in a #Justfile. I have these useful help/h recipes:

# list recipes, optionally filtered by REGEX.
@help *REGEX:
if [[ '{{ REGEX }}' == '' ]]; then just -lu; else just -lu --color=always | rg --pcre2 -i '{{ REGEX }}'; true; fi

alias h := help

and shell alias j=just; so to list foo-related scripts I’m often typing

j h foo

It's short, but… I added alias h='just help’, now it’s much better:

h foo

🎉

Unreasonably pleased by a tiny tweak to #plaintextaccounting scripts. I keep most of them in a #Justfile. I have these useful help/h recipes:

# list recipes, optionally filtered by REGEX.
@help *REGEX:
if [[ '{{ REGEX }}' == '' ]]; then just -lu; else just -lu --color=always | rg --pcre2 -i '{{ REGEX }}'; true; fi

alias h := help

and shell alias j=just; so to list foo-related scripts I’m often typing

j h foo

It's short, but… I added alias h='just help’, now it’s much better:

h foo

🎉

Unreasonably pleased by a tiny tweak to #plaintextaccounting scripts. I keep most of them in a #Justfile. I have these useful help/h recipes:

# list recipes, optionally filtered by REGEX.
@help *REGEX:
if [[ '{{ REGEX }}' == '' ]]; then just -lu; else just -lu --color=always | rg --pcre2 -i '{{ REGEX }}'; true; fi

alias h := help

and shell alias j=just; so to list foo-related scripts I’m often typing

j h foo

It's short, but… I added alias h='just help’, now it’s much better:

h foo

🎉

Unreasonably pleased by a tiny tweak to #plaintextaccounting scripts. I keep most of them in a #Justfile. I have these useful help/h recipes:

# list recipes, optionally filtered by REGEX.
@help *REGEX:
if [[ '{{ REGEX }}' == '' ]]; then just -lu; else just -lu --color=always | rg --pcre2 -i '{{ REGEX }}'; true; fi

alias h := help

and shell alias j=just; so to list foo-related scripts I’m often typing

j h foo

It's short, but… I added alias h='just help’, now it’s much better:

h foo

🎉

Unreasonably pleased by a tiny tweak to #plaintextaccounting scripts. I keep most of them in a #Justfile. I have these useful help/h recipes:

# list recipes, optionally filtered by REGEX.
@help *REGEX:
if [[ '{{ REGEX }}' == '' ]]; then just -lu; else just -lu --color=always | rg --pcre2 -i '{{ REGEX }}'; true; fi

alias h := help

and shell alias j=just; so to list foo-related scripts I’m often typing

j h foo

It's short, but… I added alias h='just help’, now it’s much better:

h foo

🎉

And the next part: importing transactions you may have forgotten but your forecast rules have not. Nicely avoids importing transactions twice.

YEAR := `date +%Y`
FORECASTJ := YEAR / YEAR + '-forecast.journal'

# import any recent transactions generated by forecast rules; --dry to preview
@import-forecast *ARGS:
hledger import -s -I --auto --forecast=-15days..tomorrow {{ FORECASTJ }} "$@"

(import explained: https://hledger.org/dev/hledger.html#import)

#hledger #PlainTextAccounting #justfile

And the next part: importing transactions you may have forgotten but your forecast rules have not. Nicely avoids importing transactions twice.

YEAR := `date +%Y`
FORECASTJ := YEAR / YEAR + '-forecast.journal'

# import any recent transactions generated by forecast rules; --dry to preview
@import-forecast *ARGS:
hledger import -s -I --auto --forecast=-15days..tomorrow {{ FORECASTJ }} "$@"

(import explained: https://hledger.org/dev/hledger.html#import)

#hledger #PlainTextAccounting #justfile

And the next part: importing transactions you may have forgotten but your forecast rules have not. Nicely avoids importing transactions twice.

YEAR := `date +%Y`
FORECASTJ := YEAR / YEAR + '-forecast.journal'

# import any recent transactions generated by forecast rules; --dry to preview
@import-forecast *ARGS:
hledger import -s -I --auto --forecast=-15days..tomorrow {{ FORECASTJ }} "$@"

(import explained: https://hledger.org/dev/hledger.html#import)

#hledger #PlainTextAccounting #justfile

And the next part: importing transactions you may have forgotten but your forecast rules have not. Nicely avoids importing transactions twice.

YEAR := `date +%Y`
FORECASTJ := YEAR / YEAR + '-forecast.journal'

# import any recent transactions generated by forecast rules; --dry to preview
@import-forecast *ARGS:
hledger import -s -I --auto --forecast=-15days..tomorrow {{ FORECASTJ }} "$@"

(import explained: https://hledger.org/dev/hledger.html#import)

#hledger #PlainTextAccounting #justfile

And the next part: importing transactions you may have forgotten but your forecast rules have not. Nicely avoids importing transactions twice.

YEAR := `date +%Y`
FORECASTJ := YEAR / YEAR + '-forecast.journal'

# import any recent transactions generated by forecast rules; --dry to preview
@import-forecast *ARGS:
hledger import -s -I --auto --forecast=-15days..tomorrow {{ FORECASTJ }} "$@"

(import explained: https://hledger.org/dev/hledger.html#import)

#hledger #PlainTextAccounting #justfile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.

Here's one for showing a near-term transactions forecast:

# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"

(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)

#PlainTextAccounting #justfile

I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.

Here's one for showing a near-term transactions forecast:

# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"

(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)

#PlainTextAccounting #justfile

I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.

Here's one for showing a near-term transactions forecast:

# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"

(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)

#PlainTextAccounting #justfile

I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.

Here's one for showing a near-term transactions forecast:

# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"

(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)

#PlainTextAccounting #justfile