#geodesic (2024-10)
Discussions related to https://github.com/cloudposse/geodesic
Archive: https://archive.sweetops.com/geodesic/
2024-10-17
v3.4.0 Enhancements
Fix ~/.aws symlink @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”2593449281” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/959” data-hovercard-type=”pull_request”…
Enhancements
Fix ~/.aws symlink @Nuru (#959) what
Restore symbolic link in $HOME to .aws Update Debian 12.6 -> 12.7 Update Python 3.12.5 -> 3.12.7 Update helm-diff 3.9.9 -> 3.9.11
why
Fixes…
Nuru has 22 repositories available. Follow their code on GitHub.
what
Restore symbolic link in $HOME to .aws Update Debian 12.6 -> 12.7 Update Python 3.12.5 -> 3.12.7 Update helm-diff 3.9.9 -> 3.9.11
why
Fixes /conf/.aws symlink is not properly creat…
2024-10-28
Does anyone incorporate any cool custom tooling into their Geodesic images? We recently added glow for markdown reading which has made the developer experience nice
@Erik Osterman (Cloud Posse) likes a lot of cool tools, but we do not distribute them with Geodesic to keep the image size down.
We do include fzf, which can be very powerful if you get into it.
A command-line fuzzy finder
@Michael have a screenshot handy?
ah, yes this one
Render markdown on the CLI, with pizzazz!
I’ve been wondering if we should adopt https://aquaproj.github.io/
aqua Official Website
to simplify package managemnt
For sure, this was more of an exploratory question to see what other tools people are building into Geodesic that help them with their workflows. Here is a README in glow
within Geodesic
and unify “tool versions in teams, projects, and CI.”
that gives me an idea!
we should support atmos docs vpc
and it print the docs for the component in glow!
Love it! I can prototype it using some custom commands and see how our team likes the docs functionality
Here’s how the docs
command could work!
@Jeremy G (Cloud Posse) Since FZF is already installed, what do you think about implementing a reverse history search using FZF? I added this function to my preferenced.d
, and it works smoothly for quick reverse lookups:
# Add fzf to reverse search bash history
__fzf_history_search() {
BUFFER=$(history | fzf --tac --no-sort --query "$READLINE_LINE" --height 40% --reverse | sed 's/ *[0-9]* *//')
READLINE_LINE="$BUFFER"
READLINE_POINT=${#BUFFER}
}
# Bind to Ctrl+R for Bash (replaces default reverse search)
bind -x '"\C-r": __fzf_history_search'
Looks like:
I think it is fine if you want to add it yourself, but the standard bash
reverse search is what people are going to be expecting and be familiar with, so I would not want to ship an alternative by default.
@Michael can you share an animated gif?
For sure, instead of seeing the typical (reverse-i-search)
when Ctrl+R is pressed, it looks like this
Ok, let me dwell on it. It’s inline with the sort of improvements we want to make. I also hear @Jeremy G (Cloud Posse)’s concern. Want to try it out and see how natural it is.
Also, we want to move to starship
so we don’t have to maintain the advanced prompt-fu (PS1)
Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, Tcsh, Elvish, Nu, Xonsh, Cmd, and Powershell.
I really value Geodesic’s stability and appreciate how it balances that with useful features (like the prompt). I’m constantly experimenting, and for me, something like Starship doesn’t need to be built in, but having the flexibility to customize is both unique and beneficial—much like the community-driven command customization options in Atmos docs.
Personally, as a matter of taste, I don’t like the fzf
command history. Maybe, though, we should have a folder of enhancements people can just copy and paste into their personalizations, so they can pick and choose without having to reinvent things.