IRC logs for #aegir, 2016-11-22 (GMT)

2016-11-21
2016-11-23
TimeNickMessage
[11:03:41]* theMusician has joined #aegir
[11:36:11]* christefano has quit (Quit: christefano)
[12:16:37]* theMusician has quit (Quit: theMusician)
[12:55:43]* shaneonabike1 has quit (Quit: Leaving.)
[14:42:12]* cmcintosh has joined #aegir
[14:42:30]<cmcintosh>greet
[15:49:13]* gusaus has quit (Quit: gusaus)
[18:19:24]* theMusician has joined #aegir
[18:21:46]* theMusician has quit (Client Quit)
[18:25:41]* boshtian has joined #aegir
[18:31:17]* theMusician has joined #aegir
[18:41:23]* cmcintosh has quit (Quit: Leaving...)
[18:55:45]* theMusician has quit (Quit: theMusician)
[19:15:28]* ybabel has joined #aegir
[21:12:14]* oluabbeys has joined #aegir
[21:17:30]* oluabbeys1 has joined #aegir
[21:19:08]* oluabbeys has quit (Ping timeout: 265 seconds)
[21:19:09]* oluabbeys1 is now known as oluabbeys
[21:56:09]* oluabbeys1 has joined #aegir
[21:56:45]* oluabbeys has quit (Ping timeout: 268 seconds)
[21:56:45]* oluabbeys1 is now known as oluabbeys
[22:08:28]* oluabbeys has quit (Ping timeout: 268 seconds)
[22:30:50]* mengi1 has quit (Read error: Connection reset by peer)
[22:32:08]* mengi has joined #aegir
[23:30:30]* noecc has joined #aegir
[23:42:04]* oluabbeys has joined #aegir
[23:51:27]* oluabbeys has quit (Ping timeout: 268 seconds)
[23:52:07]* oluabbeys has joined #aegir
[00:59:09]* boshtian has quit (Quit: boshtian)
[01:23:08]* shaneonabike1 has joined #aegir
[02:00:22]* shaneonabike1 has quit (Ping timeout: 256 seconds)
[02:06:30]* oluabbeys has quit (Ping timeout: 268 seconds)
[02:16:32]* shaneonabike1 has joined #aegir
[02:22:48]<colan>ergonlog1c: did you guys do any work on the renewal aspect of hosting_https, or does that still need to be done? queue api i guess.
[02:23:14]<colan>er, cron api? for certificate renewals.
[02:53:35]* hestenet_ has joined #aegir
[02:55:09]* hestenet has quit (Ping timeout: 246 seconds)
[03:06:44]* shaneonabike1 has quit (Ping timeout: 260 seconds)
[03:08:12]<ergonlog1c>colan: I *think* we call the LE script on verify tasks, and that it'll automatically generate a new cert if within 30 days of expiry
[03:08:19]<ergonlog1c>but I may be wrong
[03:09:07]<colan>ergonlog1c: ok, so this could very well be working already. i'll take a look.
[03:09:13]<ergonlog1c>we'd still need a queue to ensure that verify is being run frequently enough...
[03:12:33]<colan>ergonlog1c: right. this is a verify on the site or the server?
[03:18:29]<ergonlog1c>site, iirc
[03:20:40]<ergonlog1c>colan: would you mind reviewing (and hopefully approving) the 2 merge reqs here: https://gitlab.com/aegir/aegir/merge_requests?
[03:20:49]<ergonlog1c>they're pretty basic
[03:21:31]<ergonlog1c>but I'd like to merge them before starting the MR for https://gitlab.com/aegir/aegir/issues/5
[03:22:14]<ergonlog1c>which is coming along nicely, but will be significantly bigger
[03:25:12]* theMusician has joined #aegir
[03:28:39]<colan>ergonlog1c: yup, will do. while you're waiting for me, care to review https://gitlab.com/aegir/hosting_https/merge_requests/8 ? ;)
[03:29:28]* theMusician has quit (Client Quit)
[03:31:10]<colan>ergonlog1c: why the layout management? sounds a bit front-endy for us.
[03:31:30]<colan>also, i'm part of that whole anti-panels movement.
[03:38:11]* hestenet has joined #aegir
[03:41:16]* hestenet_ has quit (Ping timeout: 260 seconds)
[03:41:30]<ergonlog1c>I'll take a look at that MR
[03:42:08]<ergonlog1c>as for Panels, everything is moving towards layout plugins, apparently
[03:42:34]<colan>ergonlog1c: what does that have to do with aegir though?
[03:42:58]<ergonlog1c>I figure we need something for some default layouts
[03:43:00]<colan>as in, why do we care about managing layouts?
[03:43:30]<ergonlog1c>how would you suggest we handle building our default UI?
[03:44:50]<colan>ergonlog1c: just pick a theme with regions that make sense, and go with that one. not sure we need to provide layout choices to users.
[03:47:49]<ergonlog1c>I'd prefer to have more flexibility than that, without having to resort to creating theme templates
[03:48:29]<ergonlog1c>I can imagine that viewing a task log might have a pretty significantly different page layout, than when viewing a list of applications
[03:48:46]<ergonlog1c>or a deployment entity
[03:48:48]* shaneonabike1 has joined #aegir
[03:49:18]<colan>ergonlog1c: i guess that's useful, but it wouldn't be the first thing i'd work on, but i generally don't worry about presentation too much.
[03:49:33]<colan>sounds reasonable.
[03:50:01]<ergonlog1c>no, it isn't a priority for me, but I don;t think it should be too much of an after-thought either
[03:50:28]<ergonlog1c>aegir's ux is one of it's most frequently criticised aspects
[03:50:45]<colan>ergonlog1c: the problem with panels is/was that it too bulky, the UX was horrendous, and users did everything though there overriding the standard way to do things.
[03:51:23]<colan>if the new stuff you're using doesn't have these problems, then i'm all for it.
[03:51:28]<ergonlog1c>well, recall that we're building an application here, not a site
[03:51:57]<ergonlog1c>so having a standard way to handle ui elements will probably come in handy
[03:52:24]<colan>ergonlog1c: let's give it a go then.
[03:52:37]<ergonlog1c>but panels 8 was refactored atop layout_pluging.module (or something like that), which is apparently being considered for core
[03:53:07]* shaneonabike1 has quit (Ping timeout: 244 seconds)
[03:53:36]<ergonlog1c>I'm not really familiar enough with it all yet to be sure
[03:54:03]<colan>i guess we can rip it out later if we choose to. doesn't hurt to experiment; maybe it's good.
[03:54:19]<ergonlog1c>but greater flexibility around altering the UI has been a frequent request
[03:54:27]<ergonlog1c>yep
[03:54:29]* colan nods
[03:54:37]<ergonlog1c>I'd be open to removing/replacing it
[03:55:10]<colan>if it's a frequent request, then let's try this thing.
[03:56:05]* boshtian has joined #aegir
[03:57:46]<colan>ergonlog1c: approved both, but i see "This merge request has unresolved discussions" for each.
[03:58:52]<ergonlog1c>ok, I'll take a look
[03:59:21]<ergonlog1c>for https/dehydrated... Do you have any plans for packaging, etc. on d.o?
[03:59:54]<ergonlog1c>lst I heard, git submodules still aren't supported in d.o's packaging scripts
[04:00:32]<ergonlog1c>so we mgiht want to go with a subtree merge or something, if that's the plan
[04:00:47]<colan>ergonlog1c: i was going to talk to you about this. the README says we're committing the library directly to the project, but then submodules are also there.
[04:01:43]<colan>i'm not sure either of these are the way to go. something like the Libraries module may make more sense until Composer is supported.
[04:02:01]<colan>what have you folks done with libraries like this generally?
[04:02:02]<ergonlog1c>I *think* we were copying the script itself from the submodule, but I don't recall anymore
[04:02:45]<ergonlog1c>we haven't really used anything similar, afaict
[04:02:54]<ergonlog1c>maybe in devshop
[04:02:57]<colan>for now i just kept both in there, but thanks for raising it.
[04:03:07]<ergonlog1c>but we'd definitely suffered from NIH syndrome
[04:04:15]<ergonlog1c>iirc, our .deb uses the hostmaster distro tarball. So, if we want to include https, we'll have to sort that out
[04:04:40]<colan>jonpugh: thoughts on managing libraries?
[04:04:58]<ergonlog1c>subtree merge should work, and provide an easy (enough) way to stay up-to-date with upstream, fwiw
[04:05:32]<colan>ergonlog1c: my final thoughts when i first thought about this were to get it stable first, and then worry about it.
[04:05:37]<colan>i can look into subtree.
[04:06:37]<colan>i'll create an issue that we can worry about when we need to start packaging.
[04:06:52]<ergonlog1c>sure
[04:07:08]<colan>for now, i'm happy wity git clone --recursive.
[04:07:13]<ergonlog1c>... I don't see any of the discussions that gitlab is complaining about...
[04:07:25]<ergonlog1c>colan: that'll work in a drush makefile too
[04:07:49]<colan>yeah, exactly. could be a pipline issue? haven't seen this msg before.
[04:08:06]<colan>ergonlog1c: people still use drush makefiles? :)
[04:08:59]<ergonlog1c>jhestrom and I are going to keep maintaining it, after it get's spun out of Drush 9+
[04:09:11]<ergonlog1c>at least until D7 goes EOL
[04:11:54]<ergonlog1c>I disabled the merge block on un-resolved discussions
[04:13:01]<colan>ok, but that doesn't explain why things are blocked.
[04:13:02]<colan>https://gitlab.com/aegir/hosting_https/issues/12
[04:13:41]<ergonlog1c>no, it doesn't
[04:13:44]<colan>looks like those merges are going through now.
[04:13:49]<ergonlog1c>I assume it's a bug in gitlab
[04:13:59]<ergonlog1c>there's a setting on the project, btw
[04:14:14]<ergonlog1c>to block merges until all discussions are resolved
[04:14:53]<colan>right. these guys are really bleeding edge so yes, bugs. i just ran into https://gitlab.com/gitlab-org/gitlab-ce/issues/24654
[04:15:36]<ergonlog1c>I guess they run their latest release, if not RCs
[04:15:45]<colan>that (boards), along with their pipeline stuff is really new. so i'm not surprised.
[04:15:55]<ergonlog1c>good way to get feedback, considering it's free/gratis
[04:16:14]<colan>seems to work for 'em ;)
[04:16:36]<colan>ergonlog1c: any other thoughts on my MR?
[04:17:04]<ergonlog1c>I should have some initial commits on adding some basic entities by eod
[04:17:33]<colan>ergonlog1c: hey, scaffolding is good. take your time.
[04:17:48]<ergonlog1c>they won't yet have any interesting functionality, just crud+l10n+revisions
[04:18:01]<ergonlog1c>and testing of all that
[04:18:11]<ergonlog1c>or most, anyway
[04:18:17]<colan>thumbs up
[04:18:57]<ergonlog1c>well, that'll then give us somewhere obvious to put all our "real" functionality
[04:21:00]<colan>ergonlog1c: let me know about my MR as I need that to move forward.
[04:27:38]<ergonlog1c>colan: I'd given it a thumbs up )
[04:28:01]<ergonlog1c>is https set up for approvals now too?
[04:30:41]<ergonlog1c>colan: is there something specific you'd like me to do? I don't really have any comment beyond +1
[04:31:22]* christefano has joined #aegir
[04:34:09]<colan>ergonlog1c: ah, ok. was just thinking you'd merge it. i can do that if you looked it over.
[04:34:16]<colan>no, haven't set that up yet.
[04:34:47]<ergonlog1c>sorry, I thought you'd asked for a review :p
[04:35:00]<colan>:)
[04:35:45]<colan>now i should be able to try running this thing...
[04:55:10]* hestenet_ has joined #aegir
[04:58:23]* hestenet has quit (Ping timeout: 245 seconds)
[05:56:33]* ybabel has quit (Quit: ybabel)
[06:25:38]* shaneonabike1 has joined #aegir
[06:31:06]* shaneonabike1 has left #aegir ("PART #drupal-commerce :PART #sovereign :PING 1479843065")
[06:44:21]* hestenet_ has quit ()
[06:44:34]* hestenet has joined #aegir
[07:01:26]* shaneonabike1 has joined #aegir
[07:29:15]* noecc has left #aegir ("pax")
[08:22:51]* gusaus has joined #aegir
[09:04:50]* boshtian has quit (Quit: boshtian)