summaryrefslogtreecommitdiff
path: root/deployment
AgeCommit message (Collapse)Author
12 hoursadjust SSH entries for aisaka to route via www subdomainHEADtestmasterMarek Paśnikowski
13 hours(deployment systems aisaka): optimize DNS records to properly separate the ↵Marek Paśnikowski
two addresses
18 hours(deployment systems aisaka): add FQDN to hostsMarek Paśnikowski
26 hours(deployment systems aisaka): listen for DNS traffic on all interfacesMarek Paśnikowski
26 hours(deployment systems aisaka): rename the Otvarta address to mxMarek Paśnikowski
5 days(deployment): install Spacemacs on all instances of user 1000Marek Paśnikowski
11 days(deployment systems aisaka): add A record for Otvarta IPMarek Paśnikowski
2026-02-28(deployment systems aisaka): reindent entire module to Emacs standardMarek Paśnikowski
2026-02-27(deployment systems aisaka): set Knot to listen on Otvarta IPMarek Paśnikowski
2026-02-27(deployment systems aisaka): remove ns.marekpasnikowski.pl from DNSMarek Paśnikowski
2026-02-27(deployment systems aisaka): add ns2.marekpasnikowski.pl to DNS recordsMarek Paśnikowski
2026-02-27(deployment systems aisaka): make ns1.marekpasnikowski.pl authoritativeMarek Paśnikowski
2026-02-27(deployment systems aisaka): configure Knot to listen on all interfacesMarek Paśnikowski
2026-02-27(deployment systems aisaka): set ns1.marekpasnikowski.pl to the new IPMarek Paśnikowski
2026-02-05(deployment systems rakan): keep SSH clients aliveMarek Paśnikowski
2026-01-31(deployment systems rakan): install spacemacsMarek Paśnikowski
2026-01-24aisaka: modernize the coding styleMarek Paśnikowski
2026-01-20rakan: implement home-l2mdMarek Paśnikowski
2026-01-10aisaka: implement ip setup for a default route on a secondary WANMarek Paśnikowski
2026-01-09aisaka: set up static networking for two WANsMarek Paśnikowski
2025-12-25aisaka: add a new IP for email transportMarek Paśnikowski
2025-12-19aisaka: clean up the DNS configurationMarek Paśnikowski
The current DNS configuration is in an old style. Before attempting to point an MX record at a new IP address it is a good idea to bring the configuration up to a current style standard. * deployment/systems/aisaka.scm (ip-multimedia): define a variable to store the current static address. * deployment/systems/aisaka.scm (spf-value): construct an SPF record using the ip-multimedia variable. * deployment/systems/aisaka.scm (ttl): define a variable for DNS TTL values. * deployment/systems/aisaka.scm (marekpasnikowski.pl.zone): rename to marekpasnikowski.pl-entries; align elements in columns; utilize the new ip-multimedia, spf-value and ttl variables to remove code repetition and improve clarity. * deployment/systems/aisaka.scm (marekpasnikowski.pl-zone): define the zone-file record in a new variable; update the serial number. * deployment/systems/aisaka.scm (master-zone): use the new marekpasnikowski.pl-zone variable to configure the zone field.
2025-12-16rakan: reformat system definitionMarek Paśnikowski
The system definition was jumbled up in a single let* call, with doubled spaces and deep nesting. This commit reshapes the definition in accordance with my newest formatting standard. * deployment/systems/rakan.scm (operating-system): do this.
2025-12-16systems: export default label generation to (sovereign systems)Marek Paśnikowski
It is not possible to otherwise construct a nice-looking definition of a system label. That is because of a restriction by a lexical scope requirement. The gnu:system:operating-system-default-label funciton is instead called in (sovereign systems) module. * deployment/systems/aisaka.scm (operating-system): do this. * deployment/systems/akashi.scm (operating-system): do this. * deployment/systems/asakura.scm (operating-system): do this. * deployment/systems/cokolwiek.scm (operating-system): do this. * deployment/systems/mcdowell.scm (operating-system): do this. * deployment/systems/rakan.scm (operating-system): do this.
2025-11-22rakan: implement a Samba share to accept scansMarek Paśnikowski
* deployment/systems/rakan.scm (samba-configuration, samba-service): define the configuration records. * deployment/systems/rakan.scm (system): add Samba to the list of services.
2025-11-22implement guix offload in akashiMarek Paśnikowski
* deployment/keys.scm (akashi-guix): define guix signing key. * deployment/systems/aisaka.scm (guix-offload-rakan): add guix signing key of akashi. * deployment/systems/akashi.scm (offload-hub, guix-offload-targets, offload-extension): define guix offload configuration. * deployment/systems/akashi.scm (services): add guix offload service and clean up the definition. * deployment/systems/akashi.scm (operating-system*): clean up the definition.
2025-11-20deployment: implement build offloading from aisaka to rakanMarek Paśnikowski
* deployment/keys.scm (aisaka-guix): define signing key of Guix daemon in aisaka. * deployment/systems/aisaka.scm (rakan-machine, guix-offload-rakan, offload-rakan): define the offload target. * deployment/systems/aisaka.scm (system): add the offload configuration to the list of services. * deployment/systems/rakan.scm (guix-offload-authorizations): change the authorized signing key to aisaka's. * deployment/users.scm (openssh-configuration): add the public SSH key of marek@aisaka.
2025-11-16gitolite: disable admin-pubkeyMarek Paśnikowski
* deployment/systems/aisaka.scm (gitolite): turn off the declarative entry of admin keys, as it is impossible to add more than one.
2025-11-13deployment: create (deployment keys) moduleMarek Paśnikowski
* deployment/keys.scm: define a module. * deployment/keys.scm: define variables mcdowell-guix and rakan-guix. * deployment/systems/mcdowell.scm (guix-offload-rakan): use the new key definition at rakan-guix. * deployment/systems/rakan.scm (guix-offload-authorizations): use the new key definitions at mcdowell-guix. * keys/guix/mcdowell-signing-key.pub: remove the file. * keys/guix/rakan-signing-key.pub: remove the file.
2025-11-12add marek@mcdowell to gitolite admin keysMarek Paśnikowski
2025-11-12replace admin-pubkey in gitoliteMarek Paśnikowski
2025-11-12implement offloading prototypeMarek Paśnikowski
2025-10-17systems: rename ayase to asakuraMarek Paśnikowski
2025-09-18rakan: use default channelsMarek Paśnikowski
2025-09-15akashi: maximise coolingMarek Paśnikowski
2025-09-12rakan: add guix-rust-past-crates-channelMarek Paśnikowski
2025-09-12add initial home-environment to id1001Marek Paśnikowski
2025-09-10deployment: add uid1001 to cokolwiekMarek Paśnikowski
2025-09-10deployment: add users module with an initial password definitionMarek Paśnikowski
2025-09-08ayase: uninstall gnome-boxesMarek Paśnikowski
2025-09-07systems: add cokolwiek systemMarek Paśnikowski
2025-09-05systems: split identities of mcdowell and rakanMarek Paśnikowski
2025-09-04mcdowell: dodaje listę kanałów do guixMarek Paśnikowski
2025-08-27mcdowell: install guix-publish-serviceMarek Paśnikowski
2025-08-17mcdowell: delete distribution-channel from (guix-configuration)Marek Paśnikowski
2025-07-27aisaka: add sejf.marekpasnikowski.pl to certbotMarek Paśnikowski
2025-07-26aisaka: add sejf subdomainMarek Paśnikowski
2025-07-24aisaka: disable Distribution channel in cgitdedistributionMarek Paśnikowski
2025-07-24delete remaining bindings to Distribution channelMarek Paśnikowski
This removal is part of a process to decomission Distribution channel. --- The ultimate goal is to move useful code from Distribution channel to either Sovereign or Deployment channel. Everything else will be deleted and ultimately will be removed from network. --- Module (deployment systems aisaka) has a dangling import of (suweren update). Module (deployment users id1000) uses update-commands from (suweren update). Guix-channel file includes dependency on Distribution channel. --- The dangling import of (suweren update) is deleted from (deployment systems aisaka). The update-commands binding is replaced with a definition from Sovereign channel. The dependency on Distribution channel is removed from the list. --- With this change Deployment channel is completely independent of Distribution, which can be deleted now.
2025-07-23[4] systems: delete imports of (suweren system) moduleMarek Paśnikowski
This removal is part of a process to decomission Distribution channel. --- The ultimate goal is to move useful code from Distribution channel to either Sovereign or Deployment channels. Everything else will be deleted and ultimately will be removed from network. --- The (suweren system) module was imported in aisaka, akashi and ayase systems. --- All these imports are deleted. --- After this (suweren system) module can be deleted from Distribution channel.