Ticket #477 (closed task: fixed)

Opened 13 years ago

Last modified 12 years ago

[WG][M] MOLES Browse install instructions

Reported by: selatham Owned by: lawrence
Priority: critical Milestone: System Integration
Component: community Version:
Keywords: Cc:

Description


Change History

comment:1 Changed 13 years ago by selatham

  • Priority changed from blocker to critical

comment:2 Changed 13 years ago by lawrence

  • Status changed from new to assigned

comment:3 Changed 13 years ago by lawrence

  • Milestone changed from SystemIntegrationOctober2006 to Documentation_preBeta

comment:4 Changed 12 years ago by selatham

Bryan - you've done this haven't you? Barring updating after people have tried it.

comment:5 Changed 12 years ago by lawrence

I don't want to close the ticket someone has actually used it ...

comment:6 Changed 12 years ago by mggr

Installed browse service from instructions without too much head-scratching - about ~3hrs, mostly due to PML's webserver setup. Minor notes added to wiki page. Only a couple of tiny modifications needed - one-liners and probably PML-specific.

Instructions got me to a working browse service pretty easily, though PML's B service isn't working at the moment (not an install issue).. Test service at  http://wwwdev.npm.ac.uk/rsdas/projects/ndg/browse

Should be safe to close this now :)

comment:7 Changed 12 years ago by mggr

Added comments on SELinux.

Fixed the icons on PML's browse - it was just a config thing relating to the /layout/ directory not being in the document root (possibly worth writing up a bit of this for the howto, but mostly it'd be comments in the config files). Also created a really horrible PML custom logo to encourage Pete to get a NEODAAS logo made ;)

comment:8 Changed 12 years ago by pmiller

We have got a NEODAAS logo - use the banner from the NEODAAS website. Also, migrate from /rsdas/projects to www.neodaas..../projects/ndg/.

comment:9 Changed 12 years ago by lawrence

  • Status changed from assigned to closed
  • Resolution set to fixed

I think this can be closed now; obviously we can do more ... but the substantive task is done.

Note: See TracTickets for help on using tickets.