← Back to team overview

hkcr-dev team mailing list archive

HKCR Meeting Followup

 

Hi Felipe,

There are some differences in Plone 4 and these guys take a very
low-level approach to building Plone.   However, I want us to reuse the
Unified Installer and then HKCR will become an addon egg for Plone.

This will make it a lot easier for our target market to install.

I am just getting the directory structure down now.  But you should be
able to Install Plone 4 b5 and then branch the trunk of hkcr into the
zinstance/src directory.  Please see the attached install notes.  These
are crude at this time but I'm sure you can work with them.

I should have the oship and mlhim code installed by early next week and
we can begin working with content types.

Any questions please email me but PLEASE CC the hkcr-dev list. 

Cheers,
Tim


-- 
***************************************************************
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org 

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home 

Download and Install Python 2.6.5 (if you do not have it)

Download Unified Installer

create a directory named HKCR

Install Plone using:
./install.sh standalone --target=<path to your HKCR directory>
 --password=abc123

change directory to HKCR/zinstance

bin/buildout

bin/plonectl start

browse to http://localhost:8080

Create new plone site

login with user: admin   password: abc123

Site Id: hkcr
Site Title: Healthcare Knowledge Component Repository (HKCR)

Select OpenID and Working Copy Addons

Click Create Plone Site

Your HKCR Plone Site should be running as:
http://localhost:8080/hkcr 

If all seems to be working well continue.  Otherwise discover why your Plone site did not build.

Then in your terminal: bin/plonectl stop 

rename buildout.cfg to buildout.cfg.original

cd src

bzr branch lp:hkcr

cd ../..

copy src/hkcr/hkcr-dev.cfg to your HKCR/zinstance directory 
copy src/hkcr/buildout.cfg to your HKCR/zinstance directory
copy src/hkcr/base.cfg to your HKCR/zinstance directory
copy src/hkcr/versions.cfg to your HKCR/zinstance directory
copy src/hkcr/zope_versions.cfg to your HKCR/zinstance directory

bin/buildout -c hkcr-dev.cfg 

bin/plonectl start 

Be sure that your site still loads at:
http://localhost:8080/hkcr

Put your site in development mode:
http://localhost:8080/hkcr/manage
Go to the portal_css object and click on it.  
Now check the Development mode box; scroll all the way down and click Save.




Attachment: signature.asc
Description: This is a digitally signed message part