Assuming you want all configuration in the init script, [0] here&#x27;s the OpenRC equivalent. The USER&#x2F;ENV&#x2F;WKDIR variables are there for legibility.<p><pre><code>  #!&#x2F;sbin&#x2F;runscript
  
  USER=&quot;--user nobody --group nobody&quot;
  ENV=&quot;--env PATH=&#x2F;usr&#x2F;bin:&#x2F;usr&#x2F;local&#x2F;bin --env NODE_ENV=production&quot;
  WKDIR=&quot;--chdir &#x2F;var&#x2F;www&#x2F;blah&quot;
  
  description=&quot;Blah app&quot;
  command=&quot;&#x2F;var&#x2F;www&#x2F;blah&#x2F;bin&#x2F;www&quot;
  start_stop_daemon_args=&quot;$USER $ENV $WKDIR&quot;
</code></pre>
Assuming you had a &quot;multi-user&quot; runlevel on your system and the service was named &quot;blah&quot;, you would do the following to add that service to it:<p><pre><code>  rc-update add blah multi-user
</code></pre>
But, the &quot;default&quot; runlevel is probably the equivalent to systemd&#x27;s multi-user runlevel. So:<p><pre><code>  rc-update add blah default
</code></pre>
Describe works as expected:<p><pre><code>  $ &#x2F;etc&#x2F;init.d&#x2F;blah describe
   * Blah app
</code></pre>
[0] Real init scripts make use of OpenRC&#x27;s machinery for processing config files in &#x2F;etc&#x2F;conf.d