I switched my first root server to OVH as it was "one of the main Proxmox VE hosting partners". I hade a fatal error with my instance, and they don't actually have real technical support guys who know enough about Proxmox.
I stick with it only "because". If my yearly services go about and I deem the move worthy the potential pain, I may go back.
Unaffiliated Selfhostable Implementation: wakapi
cruft allows you to maintain all the necessary boilerplate for packaging and building projects separate from the code you intentionally write. Fully compatible with existing Cookiecutter templates. Using cruft , you can make sure your code stays in-sync with the template it came from for you.
I recommend the usage of cruft in all of my cookiecutters.
Through the use of all-repos and some little neckbeard script of mine I easily ensured all of my projects (in the linked case, ansible roles) stay up-to-date with little effort.
The diagramming program for everything. Open Source.
Features I love:
.png, .svg and html -
all without loosing meta information.
Note: I recommend attaching .drawio to the filename
to make the actual file type obvious, e.g. Networkdiagram.drawio.png.The shapes I use for Network Diagrams are:
It was all really intuitive and head-on start.
I recommend and show it to literally everyone. There is no exception.
Pandoc (the most universal file converter) can be used from the web through pandoc.org/try (official, FOSS, text-input/output) and alldocs.app (FOSS, file-input/output). I have both of these sites bookmarked in my Programming bookmarks.
When I work with Java, I use IntelliJ IDEA. When I want super-b Refactoring and Search/Replace Functionality, I use IntelliJ.
When working on anything else, I've chosen to adopt Visual Studio Code - a IDE that implements many features important and interesting to the developer experience and doesn't make me miss many things from Jetbrains while being so lightweight that I install it everywhere, even when I would've just wanted to install Notepad++.
I install it everywhere, and if it's my machine, I sign into my GitHub Account to sync all Extensions and Settings and unlock all GitHub seamlessness-capabilities.
The browser-only capability is awesome and allows for extremely seamless and fast ad-hoc development from anywhere just by signing in to GitHub.
I only really use the GUI/Side-Bar Tools "Project Manager", "GitLens", "Git Graph" and "Git History". But i do have installed many other Developer Experience changing extensions as well. For the interested, you can take a look at my VS Code Extensions I documented over at my GitHub
[Addendum 2022/08] I recently found out about that VSCode also has Live Share Extension, similiar to the one Jetbrains added in one of the newer versions. Very neat and nicely implemented over SSH too. https://docs.microsoft.com/en-us/visualstudio/liveshare/
My Jetbrains History:
IntelliJ is an awesome tool. It does everything for you, without even noticing - i.e. automatic Gradle dependency installation or adding Gradle dependencies through GUI.
I really got to use most Shortcuts and enjoyed the Weekly Tips.
I can't emphasize enough how well it's Quick Fixes and Refactoring work.
It allows you to generate all kinds of boilerplate (e.g. Getter/Setter/Constructor, toString, JavaDoc). It has a ByteCode Previewer. It has an awesome Debugger.
Also: During my 4 years in apprentice as an IT-Technician in which I also worked on some Grails (Spring) Projects it also was nice that IntelliJ IDEA ULTIMATE, which I got for free thanks to an all-time available offer for students, had Grails-aware functionality. The primary functionality I'm talking about is the ability to automatically generate a graphical database diagram for by a click on the Domain Class. Experimenting with this I quickly understood all the Relation Database Paradigms and how to implement them with GORM, or how GORM translates to database through IntelliJ's Database Tab Integration.
I use GitHub as my primary code hosting, collaboration and CI/CD platform, as well as for my portfolio.
The reasons against GitHub:
The reasons for GitHub are rather simple and more pronounced:
I don't really see the use of PuTTY (itself) anymore. Albeit as it is OSS, cross-platform and solid proven software I don't mind having it installed.
For quick/ad-hoc connections I just use the terminal (Windows has an Optional OpenSSH Client too!).
For the tool that allows me to make a directory of hosts/connections with different settings I use the following tools:
For Linux I use Remmina, a Remote Desktop Client (RDP, SSH, VNC, ...).
For Windows I use SuperPuTTY.
For console connections on Windows I use TeraTerm as it presents me with a generated list of COM Ports that represent valid, working, identified Console Cable - Making me not needing to google how that works over and over again and saving time and typical console cable question headaches.
AsciiDoc belongs to the family of lightweight markup languages, the most renowned of which is Markdown. AsciiDoc stands out from this group because it supports all the structural elements necessary for drafting articles, technical manuals, books, presentations and prose.
This includes, for example, admonitions, variables, the include statement, example blocks, footnotes, keyboard macro, equations and formular support (albeid only with asciidoctor and installed plugin iirc), automatic toc and header, description lists, actually usable tables, etc ...
In combination with Antora one can built the most awesome, versioned, and Dont-Repeat-Yourself but-also "Fully-Explain-without-just-Linking" documentation ever.
GitHub has built-in support for it, albeid not for it's include directive, though that can be dealt with by using CI to invoke asciidoctor-reducer or publishing a github page that has been rendered using the asciidoctor/antora renderer.
https://docs.checkmk.com/ uses Asciidoctor. Linus Torvalds once recommended Asciidoctor (1).
Both Debian and Ubuntu Server offer various additions to improve the use-ability of many upstream Linux packages (e.g. especially Apache2). These include wrapper scripts, arguably better default settings, additional environment variables and out-of-the-box (available or pre-installed) tools, and more (e.g. Ubuntu's update-motd.d pam extension for builtin functionality of dynamic MOTDs using scripts). All are maintained to a very high standard by the developers (which can be said for all big linux distributions, of course).
The amount of packages available through apt far outweighs RHEL's yum. packages.debian.org offers a very nice and clear way to browse apt packages, with very well presented information about everything related to each (which releases have this package? short description; dependencies/recommends/suggests; downloads; all other relevant outlinks (changelog, developer info, bug tracker, ...)).
Upgrading Debian from one stable version to another is usually very easy and not painful, which is necessary considering it's relative fast releases.
Thus, my recommendation is to start out with Debian/Ubuntu Server and when you are confident enough with Linux and have moved from hand/tutorials-crafted (eventually messy) servers to precisely-defined provisioned-servers move to a RHEL distribution because you don't need the benefits of Debian anymore and should prefer RedHat's stability and confinedness to less releases and more-upstream-like Linux.
Generalist Engineer • 1 stack
JonasPammer demonstrates balanced experience across multiple technical domains with versatile stack choices.