summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-04-05matrix support for apache md key installerHEADmasterroot
2024-02-22bugfixes in SOURCES.bashroot
2024-02-22holy shit, SOURCES.bash actually almost worksroot
2024-02-22fix: function names can contain non-word charsroot
2024-02-22bash introspection experimentsroot
2024-02-17check length of sha256sum output in case of short readsroot
2024-02-17exit with error if run_primary get_primary_gtid is empty or failsroot
2024-02-17remove unused coderoot
2024-02-17improve display outputroot
2024-02-17avoid setting $PATH; now require rpc.bash to be in runtime environmentroot
2024-02-16renamesAndrew Cady
2024-02-15mariadb scriptsroot
2024-02-15wordpress-config-info integrations and improvements related to its new interfaceroot
2024-02-15ensure replication user is created on server with output to userroot
2024-02-15clean up the devnulls etcroot
2024-02-14cleanfixroot
2024-02-14cleanuproot
2024-02-14remove unused mariabackup coderoot
2024-02-14tweak outputroot
2024-02-14it so tight and it be workin to replicate n shit n keep up n verify that to ↵root
the user with its output
2024-02-14omfg replication actually worksroot
2024-02-13the slave replication seems to work with the mariadb-dump tool automatically ↵root
providing the gtid
2024-02-13refactor like a mastorroot
2024-02-13mariadb-dump based database replicationroot
we list the databases on the primary and replica server, determine which dbs the replica server needs, then send those dbs in a single tcp stream with mariadb-dump. supposedly, the CHANGE MASTER sql statements are automatically included. however, it is unclear how or whether replication is working here. also, even if replication is working right now, it probably got set up by the old code that used mariabackup's "xtra" slave info file to get the binlog position. So the testing needs to be set up to make sure that this is all OK...
2024-02-12factor our mariabackup to replace with mariadb-dump; many output ↵root
improvements; etc
2024-02-11error-handling correctness fixroot
2024-02-10database-test.bashroot
2024-02-09fixup! enable-default-ssl.bashroot
2024-02-09copy cert from apache2 to mariadbroot
2024-02-09enable-default-ssl.bashroot
logs into remote debian machine and fixes https on default-ssl to use LetsEncrypt. In one command!
2024-02-09wordpress-config-info: support for raw (unquoted) php valuesroot
2024-02-09rewrite create-wp-config with --fqdn functionality to derive entire config ↵root
from hostname
2024-02-09switch to new, more general wordpress-config-info implementationroot
this makes it very easy to read from the JSON and write out a new config and even includes the entire upstream config so that (1) you can check that you aren't overwriting changes from elsewhere; and (2) you preserve changes made manually. the whole thing is like editing a dns zone right. except it's your wordpress zone of authority. zone of user authority. it's the zone of presence authority. each machine represents a place for a human to be present!!! as such each machine represents a zone of authority for the human's machine resources including the symbolic designation resource which is the basis of currency transfer this zone of authority needs to transfer itself from seat to seat as a basic test of itself otherwise it lacks redundancy and cannot be trusted and cannot be a seat of authority at all so it must be vacatable to be stable like any position in a constitutional design which it is domain = bailiwick we need to extend the user agency into the full extent of the user bailiwick the user's domain of authority is their public key is the left-hand side of their hostname is the right-hand side of their ipv6 address thank you shiva the destroyer remembers eternally pretty nice framework for this stuff everything is in json if only everything json was in dns oh if only everything json was in dns (to the tune or tone of that jedspoemsongband song about being stranded in space)
2024-01-27simplifyroot
2024-01-27clean up tempfileroot
2024-01-26improve error reportingroot
2024-01-26cleaner evalsroot
2024-01-26factoringroot
2024-01-25"to_JSON_all -a" exports all bash variable values (whether string, array, or ↵root
assoc array) into a single JSON object
2024-01-25very nice export of all environment!root
2024-01-24support for bash arrays and associative arraysroot
2024-01-24add jq_env and jq_exports as interfaces to export_JSONroot
2024-01-24add to docs and add test caseAndrew Cady
2024-01-24avoid use of variable name even though just local would workAndrew Cady
2024-01-24documentationAndrew Cady
2024-01-24avoid invalid character in variable namesAndrew Cady
2024-01-24properly carry forward error returnsroot
2024-01-24update documentationroot
2024-01-24simplifyroot
2024-01-24export-json will ensure no output to stdout in case of errorroot