feat: add error pages to website on bekkalokk #115
felixalb
Reference in New Issue
Block a user
Delete Branch "errorpages"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ref #250 hope this should work?
lolmao kan du fikse commit author feltet
This probably works as a first draft, but I was thinking of theming not just the website, but all of our virtual hosts at once. Should've been more specific I guess. When merged, please leave Drift/issues#250 open :)
stdenv.hostPlatform.systemd540f809b8debian-latest935dfb3f3fvaluesca45470969values0da9e38060New backup server just dropped! This server is awfully slow, and the mdraid setup is awfully slow, and I doubt that this will be a good experience, but we now have a backup server again? - Tried Disko and nixos-anywhere - Tried using mdraid - Found that md is ancient and bad - Found that disko is 100% extra steps, and a lot more complicated and noisy than just formatting your disks yourself - Found that systemd-boot doesn't support mdraid - Found that we probably don't need to mirror the boot partition :) - Found that old hardware is slow - Found that old hardware can have poor support for iPXE with UEFI, and might do weird BIOS stuff on you when you least expect it - Reaffirmed that zfs is love Current disk layout: - mdraid for boot/root disk - 4TB WD Red with 500MiB ESP with systemd-boot, Remaining mdraid - Old? - 4TB WD Red with 500MiB Unused partition, Remaining mdraid - Old? - zfs pool "tank" for the actual backup data - 8TB Toshiba MG08 - New - 8TB Exos 7E10 - New TODO: - Document the death of Toriel on the wiki - Document Bakke on the wiki - ... describing the poco loco disk layout - Start backing stuff up - Restic? Borg? Rsync? - Make backup retention policy and zfs snapshot system - Document backup procedures Reviewed-on: #87 Co-authored-by: Felix Albrigtsen <felix@albrigtsen.it> Co-committed-by: Felix Albrigtsen <felix@albrigtsen.it>restartUnitsfor some sops secrets 93c984eda8restartUnits2b51f5b0demax-y, bekkalokk/bluemap: fix eeca8778a0render-maskoption 80980167b3CPUSchedulingPolicy=batchd3fbf09576StateDirectory+ExecStartPre7ed4906e37pkgsas an output for ease ofwhy-dependsf8af632e9dbasea9cc479445nixosConfigfunc 8997f53f8csystem->stdenv.hostPlatform.system19e7cd84c3developer experiencelabel 84eedff25fLoadCredentialto correct unit 9c356db2b2wheel7c0a233f7eenvironment.systemPackageslists 0b5eb548c0hostName5bb13f4d06stateVersionefc4c164a3stateVersion1a90981060mutableUsers(absolute state) f4d10c21e3skrott-x86_64at correct nixosConfiguration, add-sdvariants 22d45ee08dflake-inputs.jsonwhen disabled 84ca4a55f2secret.keyto sops 61f560c1d2stateVersionfrom 22.11 -> 25.11 6f57e647a5stateVersionfrom 22.11 -> 25.11 ed8aeabe27stateVersionc5bd241c65security.txt8f261c58a0BindPathsto accessdataDir67b0353a2bdiskoto default devshell 4716961baacfg.enablefceb1099cbcfg.enabledc0c8dfc8d/data5314328c77legacy-cgito the python package set b3e34291a5lsofto list of default installed packages 7378d75d3fcustomization6840a70c46It looks like you accidentally mass-pinged a bunch of people, which are now subscribed
and getting notifications for everything in this pull request. Unfortunately, they
cannot be automatically unsubscribed from the issue (removing review request does not
unsubscribe), therefore development cannot continue in this pull request anymore.
Please open a new pull request with your changes, link back to this one and ping the
people actually involved in here over there.
In order to avoid this in the future, there are instructions for how to properly
rebase between branches in our contribution guidelines.
Setting your pull request to draft prior to rebasing is strongly recommended.
In draft status, you can preview the list of people that are about to be requested
for review, which allows you to sidestep this issue.
This is not a bulletproof method though, as OfBorg still does review requests even on draft PRs.
05cc46d3a1to914458d4b0914458d4b0to1973989be9Feel free to ignore review if this is still WIP, but plz fix before merge
@@ -4,0 +3,4 @@services.nginx = {enable = true;appendHttpConfig = ''error_page 500 502 503 504 /500.html;Grouping 502, 503 and 504 together isn't awful imo, but presenting them as 500 can be very misleading. Could we have different pages for the different status codes, or remove the "Intern Serverfeil"-title and "500: Intern serverfeil"-headings?
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.