kore-doc

The kore documentation found under https://docs.kore.io/
Commits | Files | Refs | README | git clone https://git.kore.io/kore-doc.git

running.md (1429B)



      1 # Running applications
      2 
      3 Starting Kore applications is done in one or two ways:
      4 
      5 * Using _kodev run_
      6 * Using _kore -c config_
      7 
      8 The first method will keep the process in the foreground allowing you to shut it down using CTRL-C.
      9 
     10 This method is aimed at developing.
     11 
     12 The second method will read the configuration file passed on the command line, load in all required application modules and attempt to change root and drop privileges accordingly.
     13 
     14 This method is aimed at running in production.
     15 
     16 You can skip chroot\(\) and privdrops using -n and -r.
     17 
     18 ## Startup sequence
     19 
     20 When Kore starts it will spawn several new processes such as the worker
     21 processes, the keymgr process and acme process (if required).
     22 
     23 Kore will check that each process starts properly within a certain
     24 time frame. If a process fails to start Kore will log the last output
     25 of this process and terminate itself.
     26 
     27 ### Random
     28 
     29 **Important** If you are running Kore chrooted and privilege separated (which
     30 you **should** be doing production), Kore will require /dev/urandom to be
     31 created under the chroot environment for both the keymgr and worker processes.
     32 
     33 Failing to do so will prevent your application from working.
     34 
     35 ### Halting applications
     36 
     37 When you wish to shutdown your application gracefully you can send a SIGQUIT or SIGTERM signal to the parent process. You can find the PID for this parent process in the pidfile you specified in your configuration.
     38