I've been using sdkman for about a decade now and am totally pleased w/ it. It does a very good job of managing JDK versions for you and much more, eg SBT, Gradle, Scala, Groovy, Leiningen, SpringBoot, ...
Now, technically you could use sdkman in your CI/CD pipeline too but I'd find it a strong smell. I've always used dedicated images pre-configured for a particular JDK version in the pipeline.
I work primarily on the JVM & the projects (personal/corporate) I work w/ can be summarised as below:
Building & running the repo is done on the host using an SCM (software configuration management tool) such as Gradle or SBT.
The external dependencies of the repo, such as Redis, are managed via adocker-compose.yml.
The README contains a short series of commands to do different tasks RE (1)
However one approach that I've always been fond of (& apply/advocate wherever I can) is to replace (3) w/ a Makefile containing a bunch of standard targets shared across all repos, eg test, integration-test. Then Makefiles are thinly customised to fit the repo's particular repo.
This has proven to be very helpful wrt congnitive load (and also CI/CD pipelines): ALL projects, regardless of the toolchain, use the same set of commands, namely
make test
make integration-test
make compose-up
make run
In short (quoting myself here):
Don't repeat yourself. Make Make make things happen for you!
I appreciate my post may sound like a criticism of lemmy.ml (and hence the downvotes.) It's not. As I said, I'm genuinely trying to see if there's anything I can do to give back to one of my (few) favourite online communities.
That said, it seems like no one else shares my views. And that is understandable 🤷♂️
Recently, I've found myself posting more often on Mastodon a Lemmy & blog way less - indeed credits go to Fediverse and the mods for making it a safe and welcoming place ❤
It's not self-hosted, rather I'm using Google's blogspot. I used to host my own website and two dozens of clients' and friends' until a few years ago (using Plone and Zope.) But at some point, my priorities changed and I retired my rock-solid installations and switched to blogspot.
That's a good question 💯 In my case too, it took me some time (read years 😂) to figure out what I'm comfortable w/.
I can think of 3 major ways that you can navigate the filesystem while being able to drop to a shell when you need it:
If you're familiar w/ Emacs, you can either:
Use dired and tramp on your machine to access/navigate the target machine.
Install Emacs (emacs-nox) on the target machine, SSH and then run emacs-nox and voila! No need for tramp in this scenario.
Use Midnight Commander (mc) which offers a TUI pretty much like Norton Commander (nc) from the days of yore.
Get used to the semi-standard structure of the file system and just use plain Bash (cd, pushd & popd) to move around. That is
Understand what usually goes into common directories (like /usr/share or /opt) and try to follow the same pattern when rolling your own software installations.
Learn how to use your distro's package manager to query packages and find out where things, like configurations and docs, are stored. Something as simple as rpm -q --list is what you usually need.
I'm not on a Debian-based system but a recent experience w/ packaging a software as a DEB was quite eye-opening 😅 The format and the build process felt too cluttered (to me) and it wasn't easy for me to wrap my head around it.
I'm happy that folks are working on alternatives ✌️
I'd find it a useful thing to have too 👍 Please see https://lemmy.ml/post/4196612 for a similar post (by me.)
Not a show-stopper in any way though 💪