Update isaw.web/README.txt

[skleinfeldt]

Review and fix this documentation to describe the steps (including any manual ones) needed to create a local dev environment with the new theme and all associated goodies.

[skleinfeldt]

@paregorios it might be efficient for you and/or @k2soule to take a quick pass through to fix any obvious errors and note any specifics you are looking for.

[paregorios]

@skleinfeldt will do

[paregorios]

I have made a few comments in the PROD_SNAPSHOT.txt file and pushed these. Am now blocked as follows:

Followed recipe in PROD_SNAPSHOT.txt locally.

Got to the following line, which executed (as shown) without any console errors:

$ bin/supervisorctl start all
client1: started
client2: started

Tried to browse to 127.0.0.1:8081 but got nothing but sit-and-spin. Tried to browse to localhost:8081. Same thing. No response to browser.

Executed:

$ bin/supervisorctl stop all
zeoserver: stopped
client1: stopped
client2: stopped

Then tried this:

$ bin/client1 fg
2015-08-05 17:48:08 INFO ZServer HTTP server started at Wed Aug  5 17:48:08 2015
    Hostname: 0.0.0.0
    Port: 8081
Hold on to your hats folks, I'm a-patchin'
2015-08-05 17:48:10 WARNING PrintingMailHost 

******************************************************************************

Monkey patching MailHosts to print emails to the terminal instead of
sending them.

NO MAIL WILL BE SENT FROM ZOPE AT ALL!

Turn off debug mode or remove PrintingMailHost from the Products
directory to turn this off.

******************************************************************************

2015-08-05 17:48:10 INFO ZEO.ClientStorage zeostorage ClientStorage (pid=579) created RW/normal for storage: '1'
2015-08-05 17:48:10 WARNING ZODB.blob (579) Blob dir /Users/paregorios/Documents/files/I/isaw.web/var/blobstorage/ has insecure mode setting
2015-08-05 17:48:10 INFO ZEO.cache created temporary cache file '<fdopen>'
2015-08-05 17:48:10 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:10 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:15 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:15 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:25 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:25 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:45 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:48:45 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:49:25 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:49:25 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:50:45 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED
2015-08-05 17:50:45 WARNING ZEO.zrpc (579) CW: error connecting to ('127.0.0.1', 8001): ECONNREFUSED

Same behavior in the browser. No additional messages written to console.

I appear to be blocked.

[cguardia]

Tom, if you were trying to copy over the production db, the clients can take several minutes to respond, because it takes some time for ZEO to process the new Data.fs.

[cguardia]

Also, does the user that runs ZEO have read and write permission on the Data.fs file?

[paregorios]

I left things up and running all night, no change: sit and spin. No console error messages. Permissions checked.

[alecpm]

These errors indicate that your zeo server is not running (or at least not accepting connections). I would suggest stopping supervisor (bin/supervisorctl shutdown), and then starting the zeoserver in the foreground to see what's going on (bin/zeoserver fg). That should give you an idea of what's causing the server to not accept connections or fail in starting. There is also a zeo log in var/log/zeoserver.log, pasting that would be helpful if running fg doesn't clarify the issue.

[paregorios]

Thanks. Not critical at this stage for predeployment. Punting to backlog for later reveiw.

[paregorios]

transferred to isawnyu/isaw.web#90