svn commit: r1644329 - /incubator/nifi/site/trunk/content/development/quickstart.md

[tk...@apache.org]

Author: tkurc
Date: Wed Dec 10 03:47:33 2014
New Revision: 1644329

URL: http://svn.apache.org/r1644329
Log:
better quickstart

Modified:
    incubator/nifi/site/trunk/content/development/quickstart.md

Modified: incubator/nifi/site/trunk/content/development/quickstart.md
URL: http://svn.apache.org/viewvc/incubator/nifi/site/trunk/content/development/quickstart.md?rev=1644329&r1=1644328&r2=1644329&view=diff
==============================================================================
--- incubator/nifi/site/trunk/content/development/quickstart.md (original)
+++ incubator/nifi/site/trunk/content/development/quickstart.md Wed Dec 10 03:47:33 2014
@@ -32,18 +32,18 @@ manually.
 Once that is done you can go to the assemblies/nifi directory and run
 `mvn assembly:assembly`
 
-### Running the application
+## Running the application
 
 #### ** WARNING **
 
 Without any configuration, the application will run on port 8080 and does not require any credentials to modify
-the flow. This means of running Apache NiFi should be used only for testing and in an environment where only
+the flow. This means of running Apache NiFi should be used only for development/testing and in an environment where only
 connections from trusted computers and users can connect to port 8080. Using iptables to allow only localhost connections
-to 8080 is a good start, but on systems with multiple users, also not sufficient.
+to 8080 is a good start, but on systems with multiple (potentially untrusted) users, also not a sufficient protection.
 
 #### Decompress and launch
 
-`mvn assembly:assembly` will create a tar.gz file in the target directory in assemblies/nifi. This tar.gz should
+`mvn assembly:assembly` will create a tar.gz file in the target directory in `assemblies/nifi`. This tar.gz should
 contain the full application. Decompressing the tar.gz should make a directory for you containing several other
 directories. `conf` contains application configuration, `logs` will contain log files, `bin` contains a fairly
 bare-bones script for launching the application, `nifi.sh`. Running `bin\nifi.sh` should start the application in
@@ -51,7 +51,10 @@ the foreground after trying to detect a
 
 With the default settings you can point a web browser at `http://localhost:8080/nifi/`
 
-Logging is configured by default to log to `./logs/nifi-app.log`
+Logging is configured by default to log to `./logs/nifi-app.log`. The following log message should indicate the web ui
+is ready for use:
+
+    2014-12-09 00:42:03,540 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs:
 
 
 [maven]: http://maven.apache.org/