motiejus
Joined 14 years ago
Joined 14 years ago
- search it on a search engine -> google it
- fetch it from an API -> cURL it
I.e. some bottle-necks in new code appearing only _after_ you've deployed there, which is of course too late.
It didn't help that some services had their deploy trains (pipelines in amazon lingo) of ~3 weeks, with us-east-1 being the last one.
I bet the situation hasn't changed much since.
neovim = {
enable = true;
vimAlias = true;
vimdiffAlias = true;
defaultEditor = true;
plugins = [
pkgs.vimPlugins.fugitive
pkgs.vimPlugins.fzf-vim
pkgs.vimPlugins.vim-gh-line
pkgs.vimPlugins.vim-gutentags
pkgs.vimPlugins.nvim-lspconfig
pkgs.pkgs-unstable.vimPlugins.vim-go
pkgs.pkgs-unstable.vimPlugins.zig-vim
];
extraConfig = builtins.readFile ./vimrc;
extraLuaConfig = builtins.readFile (pkgs.replaceVars ./dev.lua {
inherit (pkgs) ripgrep;
}).outPath;
}The only time I had a problem was when gitea started caching git bundles of my Linux kernel mirror, which bots kept downloading (things like a full targz of every commit since 2005). Server promptly went out of disk space. I fixed gitea settings to not cache those. That was it.
Not ever ddos. Or I (and uptimerobot) did not notice it. :)
- headscale+tailscale
- immich
- syncthing
I am not using native immich photo upload due to historical reasons and old habits. I set up native upload using immich to my child, will see in a couple of months how it pans out.
I've been using immich for ~3 months and am really happy so far. It was so good that I bought a server license[1]. ;)
Setting it up is quite simple. Most of the LoC comes from sharing the folders between my user (which owns the photos) and immich: https://git.jakstys.lt/motiejus/config/src/commit/6ecb1625e0...
> and letting powertop run in the background while on battery for a few hours to identify the worst offenders.
How do you do the analysis after running powertop in the background?
I spent quite some time trying different things to optimize it, but never got more than realistic 3 hours.
Happy with other aspects though.
I heavily used Django since version 0.96 (2007) until 1.5 (2014) (with Python 3)! Then came a long break with lower-level infrastructure work: linux kernel, perf tuning, some C, some Go and zig.
Last week I picked up Django again. After 10 years (!!!) of not even looking at it. It felt like meeting a good old friend: they are the same, but older and more mature. Conversations are the same. But better.
Things change in the tech world, often for the worse. Django changes, as it matures, for the better. The website layout, tutorial, colors, excellent release notes, `./manage.py runserver` are all the same as I remember them.
Except today it's easier, since I am much wiser in deploying and maintaining things than I was a decade ago. :)
I have used awesome for >10 years now, and the way awesome does multi-monitor support has grown into me. No other WM, wayland or X11, has offered it.
I am upset not because of X "deprecation" (still not convinced it will happen, hopeful it won't), but rather that I will, again, need to invest time and energy into something that had worked just fine for more than a decade.
I bought orange pi 5+ to replace my x86-based odroid-h2+. Will start the installation in the next few weeks. I have seen enough anecdotes people running NixOS on this chip, so feel pretty optimistic about it.
Also, #nixos-on-arm Matrix channel is amazing.