RE: [epf-dev] Problems encountered using EPF Wiki 1.5 RC1

["Straaten, Onno van der" <onno.van.der.straaten@xxxxxxxxxx>]

Hi Kristian,

Sorry for the confusion, I will try to clarify and I agree with you we need the user guide.

 

If you start InstantRails for the first time you will need reset the configuration files. With this step InstantRails sets itself up for the specific location you have put it.

 

I think you do have this folder? It is just the 8dot3 filename, for example when I create a folder ‘InstantRails-2.0-win’ and do dir /X it will look something like:

13-08-2008  11:09    <DIR>          INSTAN~1.0-W InstantRails-2.0-win

So “INSTAN~.1.0-W” is the 8dot3 name for  “InstantRails-2.0-win”

 

It is true there is a requirement for the zip files. The published site needs to be in the root of the zip-file, it fails when the site is contained in a subfolder.

 

You are almost right on the other option. It is possible to copy directly to the folder ‘bp’, not ‘wikis’. If you copy directly to ‘bp’ you can create a baseline process using the copied folder, it will appear in the drop down box. Using the baseline process you can create or update a Wiki site. In production I recommend to not upload using EPF Wiki but to use SCP/FTP to upload directly to the ‘bp’ folder.

 

To make it work I think it is best to install EPF Wiki again. I think InstantRails is ok but you need to clean the EPF Wiki database and folders and try again.

 

1.       Open command prompt window

2.       CD  to the epfwiki folder C:/INSTAN~1.0/rails_apps/EPFWiki/

3.       Set the environment: Set RAILS_ENV=production

4.       Recreate the database: rake db:drop db:create db:migrate

5.       Empty the ‘bp’ and ‘wikis’ folder

6.       Start InstantRails manager and start EPF Wiki web app

7.       Navigate http://myepfwiki in you browser

8.       Create the first user

9.       Copy EPF 1.5M3 published site to the ‘bp’ folder (alternatively change the zip and put the published site in the root and upload). I recommend you put the version numbering in the folder and zip name e.g. epfpl_r15_m3.

10.   Create the baseline process: In your browser http://myepfwiki > Manage > New Baseline Process > select the folder from the list and specify title, description

11.   Create the Wiki:  http://myepfwiki > Manage >  New Wiki > specify title folder description, I recommend ‘EPF Practices Library’, ‘epfpl’. Use short technical abbreviations for folder names.

12.   After step 11 you return the management page for the newly create wiki: in the row ‘Schedule New Update’ select ‘Select a baseline process’ and click on the baseline process created in step 10.  The update is now scheduled, the Wiki is still empty. Click ‘Update Now’ to do the actual creation. In a real production type environment you would schedule a job to do this.

 

HTH,

Onno

 

 

 

 

 

 

 

From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Kristian Mandrup
Sent: woensdag 13 augustus 2008 11:03
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] Problems encountered using EPF Wiki 1.5 RC1

 

Hi,

I recently installed the EPF Wiki in C:\InstantRails2.0 (closely following the EPF wiki install guide).
I spent a day experimenting with it. When I executed InstantRails.exe the first time, it asked if I would reset the configuration files.
I only worked when I answered "OK". Without a user guide at hand I stumbled into some roadblocks. The \templates 20080828\ project site seemed to work just fine on the surface, but ... From the front page of http://myepfwiki/

I choose "Create new page in ..." - "Templates"
I get the error: No such file or directory - C:/INSTAN~1.0/rails_apps/EPFWiki/public/bp/templates_20080828/new/guidances/termdefinitions/term_definition_template_A1183691.html

I don't have a C:/INSTAN~1.0 directory :(

Seems like some of the configuration files have not been reset!? I then tried to publish a site from EPF 1.5M3 and import it into EPF Wiki. The published site is a directory of static web files.
I then zip it and try to import. I get one folder level too much. OK, I must zip, not the containing folder but the files inside directly.

Another options seems to be to copy the site folder directly into: C:\InstantRails2.0\rails_apps\[EPFWiki]\public\wikis Initially the Wiki tells me there are 0 pages in this newly created site.

I look at the \templates 20080828\ project site and notice that it has a folder "new" containing all the content.

Magically, when I rename a folder such as \base_concepts\ (containing OpenUP base concept definitions) to \new\, suddenly I am told the Wiki has found 560 pages.
As I browse through the list of pages, I can see that the Wiki has only found the pages within the \new\ folder.
I then try to create a new page: No such file or directory - C:/INSTAN~1.0/rails_apps/EPFWiki/public/bp/templates_20080828/new/guidances/termdefinitions/term_definition_template_A1183691.html

So it seems, that my new Wiki has the same wrong configuration as the default \templates ...\ project. What to do!?

I then do a search for files with text matching "INSTAN~1.0" inside C:\InstantRails2.0 I find a log file, unzip_upload.log: Archive:  C:/INSTAN~1.0/rails_apps/EPFWiki/public/bp/Publish2..zip    creating: C:/INSTAN~1.0/rails_apps/EPFWiki/public/bp/Publish2./Publish2/   inflating: C:/INSTAN~1.0/rails_apps/EPFWiki/public/bp/Publish2./Publish2/about.htm  

I then make an educated guess that C:/INSTAN~1.0 must refer to C:\InstantRails1.0 as the file structure referenced matched that of C:\InstantRails2.0

I wonder if I could make the Wiki work simply by renaming C:\InstantRails2.0 to something where C:/INSTAN~1.0/rails_apps becomes a valid filelocation?
What have I been doing wrong in my installation process? Any ideas out there?
I sure hope an EPF Wiki User Guide is in the works...

Kristian

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.