| [12:45:36] | * viashimo has joined #aegir |
| [12:51:00] | * viashimo_ has joined #aegir |
| [12:51:00] | * viashimo has quit (Read error: Connection reset by peer) |
| [13:29:07] | * viashimo_ has quit (Ping timeout: 240 seconds) |
| [13:35:04] | * viashimo has joined #aegir |
| [18:38:58] | * Shwele has joined #aegir |
| [19:43:09] | * ServantSaber has joined #aegir |
| [19:45:27] | * Shwele has quit (Ping timeout: 240 seconds) |
| [21:29:36] | * ServantSaber has quit (Ping timeout: 244 seconds) |
| [21:46:08] | * Shwele has joined #aegir |
| [22:05:17] | <jonpugh> | helmo42[m]: gitbook.com is fantastic |
| [01:02:55] | <jonpugh> | helmo42[m]: Are you around? I'm wondering about the upgrade process in the debian package. |
| [01:03:14] | <jonpugh> | I want to build the process normally triggered by "hostmaster-migrate" to a simple drupal module. |
| [01:03:38] | <jonpugh> | If a hostmaster/devmaster update is available, automatically create a platform, if it verifies, move hostmaster to it. |
| [01:03:55] | <jonpugh> | We could hook into the site verify to ensure provision is also updated. |
| [01:06:07] | <helmo42[m]> | jonpugh: that could be tricky to run through the task queue but it might work. |
| [01:06:27] | <helmo42[m]> | the magic is in provision/debian/aegir3-hostmaster.postinst |
| [01:06:27] | <jonpugh> | the provision part, maybe... |
| [01:06:37] | <jonpugh> | but a new platform node create should be simple, yeah? |
| [01:06:43] | <jonpugh> | great thanks |
| [01:07:27] | <jonpugh> | this would be the basis for automatic updates |
| [01:08:18] | <helmo42[m]> | hostmaster-migrate just checks if the expected platform dir exists .... and fires drush make if it's not there |
| [01:19:30] | <jonpugh> | Wow, that seems like a really convoluted script... |
| [02:05:37] | * Shwele has quit (Quit: Leaving) |
| [02:51:30] | <colan[m]> | <freenode_jon "If a hostmaster/devmaster update"> jonpugh: Thanks to ergonlogic , the framework for this stuff is available via Distributions. See https://www.drupal.org/project/hostmaster/issues/2704799 for details. You help with this stuff would certainly be appreciated! |
| [02:51:31] | <hefring> | https://www.drupal.org/project/hostmaster/issues/2704799 => RFC: Add a 'distribution' content type [#2704799] => 17 comments, 1 IRC mention |
| [02:52:42] | <colan[m]> | So if a new "distribution" is available, created automatically via webhooks or polling, a new platform will be created automatically. |
| [02:55:08] | <colan[m]> | I think there's simply an Upgrade button on sites & platforms now (where no user input is needed: just move to newest platform in the distro), but this is the basis for making the process fully automated. |
| [02:57:29] | <colan[m]> | I think I explained this better at https://www.drupal.org/project/ideas/issues/2940731#comment-12560849 |
| [02:57:32] | <hefring> | https://www.drupal.org/project/ideas/issues/2940731 => Automatic Updates initiative [#2940731] => 44 comments, 1 IRC mention |
| [04:12:31] | * shaneonabike has joined #aegir |
| [04:37:24] | * viashimo has quit (Ping timeout: 244 seconds) |
| [04:43:29] | * viashimo has joined #aegir |
| [05:21:29] | * shaneonabike has left #aegir () |
| [09:48:04] | * viashimo has quit (Ping timeout: 264 seconds) |
| [09:48:11] | * viashimo has joined #aegir |
| [10:03:30] | * viashimo has quit (Ping timeout: 252 seconds) |
| [10:15:08] | * viashimo has joined #aegir |
