v0.4.0
What's new around the firecamp
There we go. The once "Road to..." article is now a review of what changed since 0.3.0
For the next versions, I'll try to document every things that are pushed to Github as they come. This article is the previous "Road to v0.4.4" as planned things are now done and the v0.4.0 tag is on.
New installer link
At the beginning it was just a Codeberg repository, then Github, so the curl installer link was a "raw content" from some git repo'. It was great for testing and works well indeed, but the link itself was long and verbose.
From that:
To that:
Org & Website renamed
Oh, the Github Org was also renamed from SherpaBasecamp to SherpaCLI, shorter and more descriptive. Other than a conceptual analogy, I never intended to actualy organise Anapurna or K1 trips.
The website hosted on the Netlify subdomain got also renamed as sherpa-cli, along with a new engine under the hood. Switched from Astro to NuxtJS, and really happy with it so far.
Shorter alias
The sh alias for sherpa was interfering with the natural flow when installing software with links via sh someLink, so in the new installs it will be just s. To rename an existing one, we can open the aliases file with sherpa aliases or aliasman -e in the default configured editor.
New Logo version and Favicon
In the move from Astro to Nuxt, I designed a new, minimalist, version of the logo. One of the purposes was to go along with light/dark variants. It represents the Sh:erpa mountain we are climbing and takes the form of a simple black or white vector.
The Favicon is derived from it but recieving the full colors without transparency, so it will work the same on light or dark browser tab.
README updates
Along the way, some little changes on the README files around the repositories were made.
Auto-build on source files save
Since we're talking WebDev comming to Bash, some sort of "dev server" was a need, so WatchExec will come into play. As it's name imply, that tool can watch for changes in the BashBox directory, and exec the sherpa build command in the background, each time we modify and save files.
The new command is called sherpa watch or sherpa w.
Let it run in a separate terminal tab, do your thing with the partials, and just call your script by it's executable name you defiened in Sherpa.yaml. That's it. Like if a bun run dev was running.
PS: watchexec is already added to the installer script. If you need it, you can webi watchexec@stable
Data CRUD helper
We already have the full set of yaml CRUD available with things like get_yaml_item "$key" "$file". And it's great because universal as long as we provide the full path to a yaml file.
I do appreciate the Eleventy way to work with data files, and we now have a less verbose wrapper for files inside the data/ folder, because of the predictable patterns.
Instead of:
Just this:
...where the first argument is the name of a yaml file in data/ directory, and the second a field name, with the rest of the logic happenning in the dataGet function instead of cluttering our actual script.
Update the Options file
That poor little thing was still saying that 'Comming soon: the Docs website', and all the new commands were obviously not listed.
Same for the Version partial
Classic oversight. Will be bumped to reflect the current state.
Still Planned:
Docs / Ressources / Articles
Not directly related to the Sh:erpa semver number, other than a common timeframe, but new articles and sections in the docs would be nice around things like: managing options and --flags, Bash learning ressources, some other "how-to".
Template repositories to be used as BashBox starter projects sounds like a good idea. Something we can clone into $SCD/boxes customise as a localBox, build and why-not share it with the others.