Crash on SmartOS - ENOENT upon "starting node lib/app.js"

[cmacrae]

Hey, first off: thank you for Semaphore!

I'm working on an Ansible role to get Semaphore rolled out to SmartOS zones.

Unfortunately I'm hitting some issues getting Semaphore up and running.
When running grunt serve, it gets to 'starting node lib/app.js', and crashes with:

    Fatal error: watch ENOENT
    Warning:  Use --force to continue.

            Aborted due to warnings.

Here's the output from grunt --verbose serve.
A lot easier to read if you use the following:
cat < <(curl -L https://gist.github.com/cmacrae/210efa232968a6d7591d/raw/2bd4fcf31b18bd180226ae609acb12ddb0506278/semaphore.log)

I'm running node v0.10.33. Could this be the problem? I see that your requirements state node.js >= 0.11.x
If that is likely the case, feel free to tell me where to go, and I'll try and hack on.

I've never worked with node before, or javascript for that matter, so please let me know if there are further debugging steps I can take to help narrow down the problem.

Thanks in advance

[matejkramny]

Hi there,

Mind trying grunt build followed by node lib/app.js?

It might actually be an issue with grunt or one of its modules..

ENOENT is one of node.js's cryptic error messages, meaning some file can't be found (executed or whatever).

If the same error happens after node lib/app.js then check if the credentials.js file is present. If that's present and it still crashes, its most likely due to us not testing on SmartOS.

Would SmartOS run docker? If so, you could try running semaphore from docker..

Best,
Matej

[cmacrae]

Hey Matej,

That got it running, I'll work it into my role :)
I'll close the issue, thanks for the help!

Kind Regards,
Calum

[matejkramny]

No probs, thanks for using Semaphore :).

We’ll hopefully be able to improve it in the not-so-distant future.. As you can see the development is kinda stale.

Matej Kramny

On 9 Dec 2014, at 10:16 pm, Calum MacRae notifications@github.com wrote:

Hey Matej,

That got it running, I'll work it into my role :)
I'll close the issue, thanks for the help!

Kind Regards,
Calum

—
Reply to this email directly or view it on GitHub #2 (comment).

[cmacrae]

Well, it seems great, we need an alternative to Tower...
I'd love to see more work on it, and look forward to contributing where I can!