anchor.diff:  	}
   ----
   
  +You can then run your application by typing `./my-application.jar` (where
  +`my-application` is the name of your artifact).
  +
   NOTE: Fully executable jars work by embedding an extra script at the front of the file.
   Not all tools currently accept this format so you may not always be able to use this
   technique.
  
positive.code: http://www.freedesktop.org/software/systemd/man/systemd.service.html[service unit
  configuration man page] for more details.
  
  In addition, the following properties can be changed when the script is written by using
  the `embeddedLaunchScriptProperties` option of the Spring Boot Maven or Gradle plugins.
  
  [cols="1,6"]
  |===
  |Name |Description
  
  |`mode`
  |The script mode. Defaults to `auto`.
  
  |`initInfoProvides`
  |The `Provides` section of "`INIT INFO`". Defaults to `spring-boot-application` for Gradle
   and to `${project.artifactId}` for Maven.
  
  |`initInfoShortDescription`
  |The `Short-Description` section of "`INIT INFO`". Defaults to `Spring Boot Application`
  for Gradle and to `${project.name}` for Maven.
  
  |`initInfoDescription`
  |The `Description` section of "`INIT INFO`". Defaults to `Spring Boot Application` for
   Gradle and to `${project.description}` (falling back to `${project.name}`) for Maven.
  
  |`initInfoChkconfig`
  |The `chkconfig` section of "`INIT INFO`". Defaults to `2345 99 01`.
  
  |`logFolder`
  |The default value for `LOG_FOLDER`. Only valid for an `init.d` service.
  
  |`pidFolder`
  |The default value for `PID_FOLDER`. Only valid for an `init.d` service.
  
  |`useStartStopDaemon`
  |If the `start-stop-daemon` command, when it's available, should be used to control the
   process. Defaults to `true`.
  |===
  
  
  
  [[deployment-script-customization-conf-file]]
  ==== Customizing the startup script with a conf file
  
  With the exception of `JARFILE` and `APP_NAME`, the above settings can be configured using
  a `.conf` file,
  
  [indent=0,subs="verbatim,quotes,attributes"]
  ----
  	JAVA_OPTS=-Xmx1024M
  	LOG_FOLDER=/custom/log/folder
  ----
  
  The file is expected next to the jar file and have the same name but suffixed with
  `.conf` rather than `.jar`. For example, a jar named `/var/myapp/myapp.jar` will use the
  configuration file named `/var/myapp/myapp.conf` if it exists. You can also use the
  `CONF_FOLDER` property to customize the location of that file.
  
  To learn about securing this file appropriately, please refer to
  <<deployment-initd-service-securing,the guidelines for securing an init.d service>>.
  
  
  
  [[deployment-windows]]
  
negative.code: 	$ sudo ln -s /var/myapp/myapp.jar /etc/init.d/myapp
  ----
  
  Once installed, you can start and stop the service in the usual way. For example:
  
  [indent=0,subs="verbatim,quotes,attributes"]
  ----
  	$ /etc/init.d/myapp start
  ----
  
  TIP: If you're application fails to start, check the log file written to
  `/var/log/<appname>.log` for errors.
  
  You can also flag the application to start automatically using your standard operating
  system tools. For example, if you use Debian:
  
  [indent=0,subs="verbatim,quotes,attributes"]
  ----
  	$ update-rc.d myapp defaults <priority>
  ----
  
  
  
  [[deployment-initd-service-securing]]
  ===== Securing an init.d service
  