| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-02-16 | renames | Andrew Cady | |
| 2024-02-15 | ensure replication user is created on server with output to user | root | |
| 2024-02-15 | clean up the devnulls etc | root | |
| 2024-02-14 | cleanfix | root | |
| 2024-02-14 | cleanup | root | |
| 2024-02-14 | remove unused mariabackup code | root | |
| 2024-02-14 | tweak output | root | |
| 2024-02-14 | it 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-14 | omfg replication actually works | root | |
| 2024-02-13 | the slave replication seems to work with the mariadb-dump tool automatically ↵ | root | |
| providing the gtid | |||
| 2024-02-13 | refactor like a mastor | root | |
| 2024-02-13 | mariadb-dump based database replication | root | |
| 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-12 | factor our mariabackup to replace with mariadb-dump; many output ↵ | root | |
| improvements; etc | |||
| 2024-02-11 | error-handling correctness fix | root | |
| 2024-01-23 | set server-id after restore from backup | root | |
| 2024-01-23 | refactors | root | |
| 2024-01-21 | move hosting-tools config into /etc/hosting-tools | root | |
| 2024-01-20 | path fixes | root | |
 |
index : hosting-tools.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiff |