Ticket #560 (closed enhancement: fixed)

Opened 3 years ago

Last modified 3 years ago

Install drupal-based project management system onto our servers

Reported by: ed Owned by: jim
Priority: major Milestone: Maintenance
Component: Unassigned Keywords:
Cc: chris, ed Estimated Number of Hours: 0.0
Add Hours to Ticket: 0 Billable?: yes
Total Hours: 2.55


Please can you install a suitable project management drupal-based tool onto the suitable server? I am thinking of Open Atrium. It's for staff and partners to use for management stuff (ie not a ticketing system or mediawiki).

Open Atrium?

Can you let me know how long it would take to install to a point where I can manage it and get a pilot project up and running?


Screen Shot 2013-06-20 at 09.13.00.png (121.9 KB) - added by ed 3 years ago.
screengrab: 502 for spaces.tn.org

Change History

comment:1 Changed 3 years ago by jim

FYI Octopus (part of BOA) can auto-install the distros on this page: https://drupal.org/project/octopus

We just need to add the correct platform code to ~/.tn.octopus for Atrium from here: http://drupalcode.org/project/octopus.git/blob/HEAD:/OCTOPUS.sh.txt#l143

Then it's just a case running octopus up-stable tn platforms (I think) to install the newly chosen platform(s) on the server.

From there we just need to set up a site on the new platform that is installed in Aegir. And set up Ed's account.

I would estimate 10-30 minutes.

comment:2 Changed 3 years ago by chris

  • Add Hours to Ticket changed from 0.0 to 0.1
  • Total Hours changed from 0.0 to 0.1

I guess Open Atrium would do the job, I'm sure it would be a lot quicker for Jim to install this if it's going to live on wiki:PuffinServer and it does make sense for all Drupal sites to use this server. If Jim does do the install and documents what was done I might feel more confident in adding sites next time -- messing around with a system I don't fully understand on a live server is something I try to avoid if possible :-)

The question that springs to my mind is what domain do you want to use? if you use something.transitionnetwork.org then HTTPS won't be a problem as we have a wild card cert and I expect that people will be only using modern browsers so they will have SNI support and a dedicated IP address won't be needed -- I'd strongly suggest the site be made HTTPS only.

comment:3 follow-up: ↓ 5 Changed 3 years ago by ed

OK thanks guys

Jim please can you:

  1. set up OA on puffin with Ed as the big cheese user so that it works with https as suggested by Chris
  2. document what you did for future reference

Chris: please can you:

  1. set up 'space.transitionnetwork.org'to point to Jim's install

comment:4 Changed 3 years ago by ed

  • Cc chris added; jim removed
  • Owner changed from chris to jim
  • Status changed from new to assigned

and add your time to this ticket JIM!

comment:5 in reply to: ↑ 3 Changed 3 years ago by chris

Replying to ed:

Chris: please can you:

  1. set up 'space.transitionnetwork.org'to point to Jim's install

No need, we have *.transitionnetwork.org pointing to wiki:PuffinServer and it has a *.transitionnetwork.org cert so it's all set up as far as I'm aware :-)

comment:6 Changed 3 years ago by ed

Jim - please can you let me know when you'll be able to knock this up?

comment:7 Changed 3 years ago by jim

Yes sorry Ed, I'll do today/tonight sometime and let you know.

I hesitated because though Atrium 1.7 is out, mature and available via Octopus, there's also the new 2.x Alpha 5 which looks tasty. I guess you want stable and proven rather than cutting edge?

comment:8 Changed 3 years ago by chris

FWIW the features lists appear to be here:

If I were you I'd be tempted to go for version 2 as that should aviod having a painful future upgrade from 1.7 to 2. But I don't know what features you need...

comment:9 Changed 3 years ago by ed

I saw the upgrade pain too - from 1.7 to 2.0 - but it was my understanding that 2.0 needed D7?

comment:10 Changed 3 years ago by jim

D7 will come as part of Atrium...

A 'platform' in Aegir speak is "Drupal core + Modules + Themes + Config + Libraries + anything else we need"... So D7 is a GOOD thing here, in that it's better than D6 and 2.x will have a longer life.

It comes down to your choice Ed -- the 1.7 will be installed in a few minutes as part of BOA, whist 2.x will need me to manually find the makefile and install that via Aegir. 2.x will have some bugs and unfinished things, whilst 1.7 will be solid but still the 'first version'.

Once the platform is on the server, any number of Atrium sites can installed on them.

An alternative is to install both and you have a play. Or you say which you'd prefer and I install that. It's not really a risk, since Aegir handles most of this.

comment:11 Changed 3 years ago by ed

Go for the D7 install Atrium 2.0. Brilliant. And keep your time tracked on this ticket. I'm doing a maintenance tally soon...

comment:12 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.25
  • Total Hours changed from 0.1 to 0.35

Done, account added for Ed and sent him notification -- check spam if you've not got it Ed.

I'll document this tonight, plus fix a few things needing attention.

Looks like lots to do/play with in there -- and you're gonna love Panopoly when you get into it (the whole site is panels-driven with pages having their own layouts & other goodies!)

comment:13 Changed 3 years ago by ed

Sorry Jim, 502 error returned after much lack of connecting. screengrab attached.
ALSO: please can you call this:



Changed 3 years ago by ed

screengrab: 502 for spaces.tn.org

comment:14 follow-up: ↓ 15 Changed 3 years ago by jim

502s were a result of Chris restarting the wrong PHP-FPM after doing work on #563 -- transient and not related to this ticket.

Renaming the site is a case of migrating in Aegir it when needed. I called it 'spaces' for two reasons:

  1. I messed up and made an assumption when I created it, sorry.
  2. Because (honestly!) the plural made more sense when the creating since Atrium can have as many spaces as required -- they're called as such on the site too.

So please carry on using the site, I'll change the url to space. from spaces. when I document the creation process.

I'll proceed as above, unless you say otherwise that my 2nd point is a good one and want 'spaces' after all!

comment:15 in reply to: ↑ 14 Changed 3 years ago by chris

Replying to jim:

502s were a result of Chris restarting the wrong PHP-FPM after doing work on #563 -- transient and not related to this ticket.

That's not exactly right -- I didn't start the wrong one today, I haven't done that for some months now ;-)

We discovered today that when the server boots it starts the wrong php-fpm. After a boot you have to manually stop the wrong one and start the right one. I'm sorry it took me 10 or so mins to realise this had happened. I'm going to now document it on the wiki:PuffinServer page

comment:16 Changed 3 years ago by jim

@Chris, no worries, apologies for casting aspersions! Interesting about the boot issue -- Babylon doesn't do that, services pop up and run ok first time when last rebooted. Is there any init.d changes you made etc?

comment:17 Changed 3 years ago by chris

I think perhaps the right php-fpm wasn't started because second.sh was commented out? But I'm not sure why it didn't start or what should start it. I expect the wrong one starts simply because it's installed and configured? I'll try to answer these questions...

Last edited 3 years ago by chris (previous) (diff)

comment:18 Changed 3 years ago by chris

php5-fpm is installed using a deb:

aptitude search php | grep fpm
i   php5-fpm                        - server-side, HTML-embedded scripting langu

The server is running at runlevel 2:

who -r 
         run-level 2  2013-06-20 09:39                   last=S

Both version of php-fpm are set to run at this runlevel:

ls /etc/rc2.d/ -lah | grep php
lrwxrwxrwx   1 root root   19 Jan 28 00:02 S01php53-fpm -> ../init.d/php53-fpm*
lrwxrwxrwx   1 root root   18 Jun  9 12:23 S01php5-fpm -> ../init.d/php5-fpm*

So I have removed this sym link to prevent php5-fpm running after the next reboot:

rm /etc/rc2.d/S01php5-fpm

And updated the documentation here wiki:PuffinServer#php-fpm

comment:19 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.55
  • Total Hours changed from 0.35 to 0.9

Right, http://space.transitionnetwork.org/ is where it's at now, not "spaces."...

I see you've been in and doing stuff Ed, how are you finding it?

Anyway, documentation on building the platform...

  • I tried the makefile that comes with the site package, but both that make file and the build.sh file that comes with the code in the profiles/openatrium folder did not work... It's alpha.
  • So I gave up 'being clever' and just did the basic way, like this:
  1. Logged in, changed to the 'tn' user, went to the 'static/scratch' folder (my working area so I don't accidentally mash a working platform):
    local-computer:$ ssh ssh jim@puffin.webarch.net
    puffin:$ sudo -i
    puffin:# totn
    tn@puffin:~$ cd static/scratch
  2. Downloaded the latest OpenAtrium release from https://drupal.org/project/openatrium, unzipped it, removed the downloaded file, finally moved the unzipped platform into the correct place in ~/static like so:
    tn@puffin:~/static/scratch$ wget http://ftp.drupal.org/files/projects/openatrium-7.x-2.0-alpha5-core.zip
    tn@puffin:~/static/scratch$ unzip openatrium-7.x-2.0-alpha5-core.zip
    tn@puffin:~/static/scratch$ rm openatrium-7.x-2.0-alpha5-core.zip
    tn@puffin:~/static/scratch$ cd ..
    tn@puffin:~/static/scratch$ mv scratch/openatrium-7.x-2.0-alpha5/ .
  3. That's all the 'linux nerd' stuff done, over to Aegir where I logged in as my account.
  4. Clicked 'Add platform', bottom right.
  5. Set 'Platform name' to OpenAtrium 7.x-2.0-alpha5, and checked the path (just under the name box but editable) was auto-generated correctly from the name - it was.
  6. No makefile (since we've already got a fully made platform downloaded, and set the two user accounts to be able to work with the platform.
  7. Click save, wait for it to build.
  8. Click 'Add site' in the tabs menu at the top of the page.
  9. Set the 'Domain name' to spaces.transitionnetwork.org (NB wrong url, should be 'space.'); left Client as admin, Chose 'OpenAtrium?' platform; set 'Cron interval' to 1 hour; in 'Domain aliases' I added 'spaces.dev.transitionnetwork.org (this gives us access to the site in dev mode on that URL, if needs be).
  10. Clicked save, waited, got emailed the link to the new site, logged in and set my password for the superuser account (available on request), and created Ed's account.

Finally, to correct the incorrect URL from "spaces." to "space.", I simply ran the 'Migrate' task on the site in Aegir, changing only the domain name.

Adding time for above, plus time to document above.

comment:20 Changed 3 years ago by jim

Done... OK Ed?

comment:21 Changed 3 years ago by chris

Could you make it HTTPS only? By, for example, redirecting all HTTP requests to HTTPS. I'd be happy to add this to the nginx configuration if you can tell me which file it should be added to.

comment:22 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.3
  • Total Hours changed from 0.9 to 1.2

Best done though a module, and on D7 there's https://drupal.org/project/securelogin which is excellent, secure, 'just works' and I use it at work on every site we make.

$ cd ~/static/openatrium-7.x-2.0-alpha5
$ drush dl securelogin
No release history was found for the requested project (securelogin‎).

Hmmm. D.org must have issues, so got it myself and enabled it:

$ cd sites/all/modules
$ mkdir contrib
$ cd contrib
$ wget http://ftp.drupal.org/files/projects/securelogin-7.x-1.4.zip
--2013-06-23 22:52:19--  http://ftp.drupal.org/files/projects/securelogin-7.x-1.4.zip
Resolving ftp.drupal.org...
Connecting to ftp.drupal.org||:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14027 (14K) [application/zip]
Saving to: “securelogin-7.x-1.4.zip”

100%[======================================================================================================================================================================================================================================>] 14,027      91.1K/s   in 0.2s    

2013-06-23 22:52:19 (91.1 KB/s) - “securelogin-7.x-1.4.zip” saved [14027/14027]
$ unzip securelogin-7.x-1.4.zip
$ rm securelogin-7.x-1.4.zip
$ drush @space.transitionnetwork.org en securelogin
The following extensions will be enabled: securelogin
Do you really want to continue? (y/n): y
securelogin was enabled successfully.                                        [ok]

All good, except on http://space.transitionnetwork.org/admin/config/people/securelogin it says:

Secure Login module expects the Drupal $confhttps? setting to be at its default value: FALSE. Because it is currently enabled, secure logins cannot be fully implemented because Drupal sets insecure session cookies during login to the secure site.

So I edited /data/disk/tn/static/openatrium-7.x-2.0-alpha5/sites/space.transitionnetwork.org/local.settings.php to add this:

// JK - Required to make Secure Login (https://drupal.org/project/securelogin) work properly.
$conf['https'] = FALSE;

And logged out/in and the secure session is now working as expected.

Last edited 3 years ago by jim (previous) (diff)

comment:23 Changed 3 years ago by ed

Thanks Jim - I've been in and added some stuff - it's either quite mysterious and/or pretty buggy; I know it's an alpha - so will set some time aside to do testing after my holiday - back in second week of July... cheers!

comment:24 Changed 3 years ago by jim

Ok, well it's still alpha so I am happy to update the platform as new releases come out if you want... I'll document that here too, but basically it's a case of downloading the new platform, adding the 'Secure Login' module, then migrating the current site to the new platform. Around 10 mins...

Let me know if you want me to keep an eye out and update accordingly.

comment:25 Changed 3 years ago by ed

Great. Please keep an eye out and update accordingly.

Please also keep your time on this ticket for this work.

comment:26 Changed 3 years ago by ed

  • Priority changed from major to minor

moving to minor - in maintenance

comment:27 Changed 3 years ago by ed

  • Priority changed from minor to major

further to phone call today - please update to the latest version - I know it's only beta 5 (?), but that's a good move onward for me to do some tinkering - hopefully there will move action over september, but let's have a look at the beta...

comment:28 Changed 3 years ago by jim

  • Cc ed added

Haven't forgotten about this but since Ed's away this can wait until his return -- that way we might get a later beta (currently beta3 -- see http://openatrium.com/download.

comment:29 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.05
  • Total Hours changed from 1.2 to 1.25

Actually, on Drupal.org the version is up to beta 4: https://drupal.org/node/2077271


comment:30 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.15
  • Total Hours changed from 1.25 to 1.4

I've installed/created a new platform for spaces using the latest dev (beta 4 + some fixes)...

However, this is now blocked by #610 - Aegir migrate tasks hang on Drushrc load.

comment:31 Changed 3 years ago by ed

they've sexed up their site and there's a new download...

comment:32 Changed 3 years ago by jim

Yarp, 2.0 is out... I'll try to nail #610 on Sunday, then that'll get us moving on a number of fronts again.

comment:33 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.25
  • Total Hours changed from 1.4 to 1.65

http://space.transitionnetwork.org/ is up! WOO!

But all pages redirect to homepage. BOO!

It's a known issue, will try to resolve now.

comment:34 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.25
  • Total Hours changed from 1.65 to 1.9

Haven't fixed this as yet... will debug tomorrow :(

comment:35 Changed 3 years ago by jim

Something to do with all /admin and /node/add pages getting a 301 back to homepage -- we've seen this before and it's a Octopus thing.

Last edited 3 years ago by jim (previous) (diff)

comment:36 Changed 3 years ago by jim

  • Add Hours to Ticket changed from 0.0 to 0.65
  • Status changed from assigned to closed
  • Resolution set to fixed
  • Total Hours changed from 1.9 to 2.55

Fixed the redirect issue...

cd /data/disk/tn/static/openatrium-7.x-2.0/sites/space.transitionnetwork.org/modules
touch allow_anon_node_add.info
touch disable_admin_dos_protection.info

Which makes it a manifestation of the issues we saw on https://drupal.org/node/1994346 (cached). So it's not session 443 that is causing the issue as we thought, but something else causing a false positive around session cookie checking.

But in any case, OA is insalled. I've also added the forced HTTPS sessions:

cd /data/disk/tn/static/openatrium-7.x-2.0/
drush dl securelogin
drush space.transitionnetwork.org en -y securelogin

Finally, I added the following to /data/disk/tn/static/openatrium-7.x-2.0/sites/space.transitionnetwork.org/local.settings.php at the behest of the Secure Login module.

// Required for Secure Login module.
$conf['https'] = FALSE;

I've now made Ed's account and set him as an admin...


Note: See TracTickets for help on using tickets.