Gaia/Email/SecretDebugMode: Difference between revisions

Gaia/Email/SecretDebugMode (view source)

Revision as of 00:12, 23 March 2013

348 bytes added , 23 March 2013

→‎Interpreting the log files

Andrew Sutherland

Confirmed users

360

edits

@@ Line 88: / Line 88: @@
    chmod a+r /tmp/gem-log.json
-== Interpreting the log files ==
+== Interpreting / viewing the log files ==
 You may just want to provide the JSON file to the developers of the e-mail application.  But if you don't, here is what you do:
-Check out a copy of arbitrarypushlog and build the standalone mode with a "?log=PATHTOLOG" argument, keeping in mind that you may need to host both the source and the log file at the same origin in order for things to work if the log file is not served with blanket CORS permissions.
+Options:
+* Check out arbitrarypushlog
-Alternatively, you can either use the index.html referenced above with "?log=LOGURL" appended or copy the files that make it up to wherever you want and CORS is not a problem.
+** use your host's own localhost server to expose the UI.  Specifically, symlink or what not your git checkout of ArbPL.
+*** use the development mode, no building required.  Use index-app.html with "?log=/PATH/TO/LOG/ON/THE/WEBSERVER".
+*** build the optimized standalone mode,then use index-standalone.html with a "?log=PATHTOLOG" argument, keeping in mind that you may need to host both the source and the log file at the same origin in order for things to work if the log file is not served with blanket CORS permissions.
+* Use an existing build of the UI, like the one linked above.  Note that this requires that the build is up-to-date.  Be sure to use"?log=LOGURL" appended or copy the files that make it up to wherever you want and CORS is not a problem.