| [22:10:03] | * shaneonabike has joined #aegir |
| [02:59:15] | * theMusician has joined #aegir |
| [02:59:37] | * theMusician has quit (Client Quit) |
| [03:31:14] | * mstenta has joined #aegir |
| [04:31:05] | * mstenta has quit (Quit: Leaving) |
| [05:43:49] | * anarchat has joined #aegir |
| [05:48:51] | * anarcat has quit (*.net *.split) |
| [07:18:39] | * shaneonabike has quit (Remote host closed the connection) |
| [08:13:19] | <jonpugh> | colan[m]: I appreciate all that effort, I'm just wondering if there might be a simpler solution, specifically for hostmaster, that could allow it to update itself. |
| [08:14:13] | <jonpugh> | since hostmaster already has update.module, I was exploring how to use that to trigger the creation of a new platform. |
| [08:14:31] | <jonpugh> | haven't spent much time on it though. |
| [08:27:53] | <jonpugh> | Thanks @helmo42[m] I've merged one of your devshop PRs, others have tests running |
| [08:50:48] | <colan[m]> | jonpugh: right. i'm just worried that a simpler solution could be (1) too hacky as per the existing aegir code we all know & love, and (2) not be generic enough to work with everything (i.e. not just hostmaster). but sure, may as well see what you can dig up. report back & let us know what you find out. |
| [08:51:20] | <jonpugh> | I mean, it would basically just replicate a manual node/add/platform and migrate task. |
| [08:51:38] | <jonpugh> | I will :) |
