Am 30.08.2012 18:06, schrieb simendsjo:
I don't know how far into the future vibedist is, or exactly what it's
trying to solve, but this might be somewhat overlapping.
I just published a site (for a programming assignment at school), and
wonder how I should start the site..I could add an rc.d entry, but as all running vibe apps is named "app",
it would only support a single site.
Could vibe use the cwd last path as the name instead of "app"?Any other good ideas of how I should handle starting the site as a
daemon when the server starts?
A recent pull request added support for naming the main entry
<packagename>.d instead of app.d, where <packagename> is the name
specified in the package.json file. The executable will then also be
named <packagename>.
But in general rc.d would also be my choice (currently I start my
watchdog script manually because the server never goes down anyway and I
wanted to wait for vibedist before putting more work into that area)