Not an answer, but you don’t need an extension to defeat right-click blocking scripts: shift-right-click usually does the trick.
Not an answer, but you don’t need an extension to defeat right-click blocking scripts: shift-right-click usually does the trick.
That goes into the work profile of my android phone and that profile of switched off after clocking out. Simple as that, I don’t have to carry two phones and get my peace after hours. And my company respects my free time which also helps s lot.
Hmm, I see. The perfectionist in me would want to shed that processor load though ^^
Without any judgement: why are your servers running X11? Just because you dislike SSH’ing to them?
Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.
Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE
part of your SQL command (or analog statement of the query builder)? No fucking thanks.
Yep, it’s a repost of this one.
One could even think this OP is an alt account.
If all of those servers are yours (which they likely are, since you get ssh access), you can use one key for all. Using different keys would make one compromised key less problematic. But if someone was able to copy one file of your system, they can copy multiple files.
That resolves keeping track of things as well 😄
Ducking Medium again. No I don’t want an account with you. The article can’t be that interesting.
You forgot the package hollywood.
I would recommend key based authentication for SSH connections. For the normal connection, the key pair is enough, if you want admin (root) access, you would use the command sudo which in turn requires a password. For creating a default admin account: Linux does this for you, it’s called root. You should create a personal user to work with in daily business and add it to the sudoers group (permits using the sudo command)
I’m a sucker for jetbrains Mono when I need a monospaced font. It just looks nice to me.
If the package comes from the repo, you can uninstall it by the same name you used to install it. If it came from a .deb file (in case of debian), you can find out how the package calls itself and use that name to uninstall. Usually the package name is quite identical to the file name. And dpkg -L
shows you which files came from the package and where they were installed.
I’m fine with config files, as long as they are where you expect them (~/.config/tool or ~/.tool). What I dislike is yet another funny config syntax because the dev couldn’t settle on an established standard. Command line syntax is ok, if you give me sensible completions.
Not a recommendation per se, but you can use any backup software as long as you can edit your live iso. For example puting the restic binary into /opt
For the maven password, ok maybe. Your ssh private key should require a passphrase.
But now you have the only credential, the REPO_TOKEN in plaintext in your .git/config file. That’s even worse.
Edit: typo
PlantUML supports Gantt charts if I remember correctly. Can run locally (java if I’m not mistaken) or via web.