Author: joewitt Date: Fri Dec 12 01:50:12 2014 New Revision: 1644809 URL: http://svn.apache.org/r1644809 Log: CMS commit to nifi by joewitt
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=1644809&r1=1644808&r2=1644809&view=diff ============================================================================== --- incubator/nifi/site/trunk/content/development/quickstart.md (original) +++ incubator/nifi/site/trunk/content/development/quickstart.md Fri Dec 12 01:50:12 2014 @@ -46,7 +46,7 @@ to 8080 is a good start, but on systems `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`. On linux (and possibly macos) running `bin/nifi.sh start` +bare-bones script for launching the application, `nifi.sh`. On linux (and possibly OS X) running `bin/nifi.sh start` should start the application in the foreground after trying to detect a Java installation. There are scripts to help with startup on windows as well. The entire concept of how the application will integrate to a given OS and run as an enduring service is something we're working hard on and would appreciate ideas for. The user experience needs to