IRC logs for #aegir, 2018-01-16 (GMT)

2018-01-15
2018-01-17
TimeNickMessage
[11:08:57]* realityloop has joined #aegir
[11:46:36]* realityloop has quit (Quit: Leaving..)
[19:16:37]* reaper013 has joined #aegir
[20:25:56]* ybabel has joined #aegir
[23:07:29]* reaper013 has quit (Ping timeout: 260 seconds)
[00:08:37]* mstenta has joined #aegir
[01:47:22]<colan>ergonlogic: do you remember how you handled composer installation in hosting_composer? do you just assume it's already installed?
[01:47:46]<ergonlogic[m]>probably, but let me check
[01:52:05]<ergonlogic[m]>Look like we're assuming Composer is installed and in PATH
[01:52:13]<ergonlogic[m]>colan: ^^^
[01:53:20]<colan>ergonlogic: that would explain the `sh: 1: composer: not found` i'm getting. thanks!
[01:53:27]<colan>any thoughts on how to tackle?
[01:53:38]<ergonlogic[m]>I'll update the project page to reflect that
[01:53:39]<colan>will just add an installation note for now.
[01:53:54]<colan>thanks
[01:55:20]<ergonlogic[m]>in Aegir5, I install drush 8.x into /var/aegir/.local/bin
[01:55:23]<ergonlogic[m]>so we could do something similar here
[01:56:58]<helmo42[m]>We don't have a hook for requirements checking in the backend ... that might be a nice addition to the concept of a module. Maybe a server verify hook could check it and set a flag that then gets shown via Drupal's normal hook_requirements
[02:00:43]<ergonlogic[m]>colan: updated https://www.drupal.org/project/hosting_composer
[02:03:10]<ergonlogic[m]>We could run "which composer" in the backend, and flag a warning/error if it comes up empty.
[02:08:45]<colan>ergonlogic: helmo42 https://www.drupal.org/project/hosting_composer/issues/2937049
[02:09:46]<ergonlogic[m]>+1
[02:16:31]* theMusician has joined #aegir
[03:14:51]<colan>https://www.drupal.org/project/hosting_composer/issues/2937068
[04:42:59]* mstenta has quit (Ping timeout: 276 seconds)
[05:00:10]* mstenta has joined #aegir
[05:27:44]<jonpugh1>ergonlogic[m]: helmo42[m] is that a link to search all issue queues still available somewhere?
[05:47:56]<colan>@freenode_jonpugh[m]:matrix.org: http://docs.aegirproject.org/en/3.x/community/#drupalorg-issue-queues
[05:48:26]<jonpugh1>thank
[05:48:27]<jonpugh1>s
[05:48:36]<jonpugh1>we should put that right on the homepage...
[06:03:38]<colan>better to have a single queue. i believe ergonlogic 's doing that for aegir5. the multiple-projects thing is what took me a while to figure out when i got started.
[06:04:10]<colan>but yeah, +1 for making that link findable.
[06:05:08]<jonpugh1>For the core project you have some freedom there... being a drupal distro, we will never escape project issues thanks to all our contrib projects :D
[06:05:45]* colan nods
[07:17:42]<jonpugh1>ok colan[m] helmo42[m] ergonlogic[m] I think I've got this composer problem solved natively provision.
[07:17:44]<jonpugh1>https://www.drupal.org/project/provision/issues/2937147
[07:53:31]<colan>@freenode_jonpugh[m]:matrix.org: added my comments there.
[07:56:28]<helmo42[m]>johnpugh: cool I'll check it out in the morning
[07:59:09]* ybabel has quit (Quit: ybabel)
[08:04:20]* theMusician_ has joined #aegir
[08:05:30]* theMusician has quit (Ping timeout: 260 seconds)
[08:05:30]* theMusician_ is now known as theMusician
[08:55:31]* theMusician has quit (Quit: theMusician)
[09:02:00]* theMusician has joined #aegir