How does the Hallway API ( singly ) schedule profile synchronising?

[filip mertens]

I am running the Hallway API on an Ubuntu server

with nodejs, mysql, s3, RIAK, redis.

Sign on works fine, however it looks like the profile information tasks ( friends ) never get called.

I can see they get stored in Redis en somethings are stored on S3 Ijod.

Are there some other daemons I need to run to allow the schedules to run?

[Kristján Pétursson]

Hi Filip,

You will need to run a worker in addition to the API host. Take at look at the contents of Procfile for the commands that start each (apihost and workersup), or if you have Foreman installed (gem install foreman), you can run `foreman start` to run everything.

Also, make sure you've added keys for the services you want to use in Config/apikeys.json. The format can be found in Config/apikeys.json.example

Hope that helps,

Kristján

--
You received this message because you are subscribed to the Google Groups "Singly API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to singlyapi+...@googlegroups.com.
To post to this group, send email to sing...@googlegroups.com.
Visit this group at http://groups.google.com/group/singlyapi?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jeremie Miller]

Yep, there's multiple "roles" that the hallwayd.js main script can start up, by default it's an apihost, but additionally to run background syncing you run "node hallwayd.js workersup" and it should pick up tasks/schedules and save out data.

Jer

[filip mertens]

Hi Kristján,

That is great information, I always did rerun ./hallway up till now. I'll try this method. 

Thanks!

Filip

Op dinsdag 19 februari 2013 19:24:05 UTC+1 schreef Kristján Pétursson het volgende:

[filip mertens]

Hi Jer,

Thanks, so the ./hallway actually doesn't do that too? I haven't really looked in too much detail at that one yet.

thanks again!

Filip

Op dinsdag 19 februari 2013 19:41:20 UTC+1 schreef Jeremie Miller het volgende:

[filip mertens]

Hi Jer,

this results in :

node hallwayd.js workersup

module.js:340

    throw err;

          ^

Error: Cannot find module 'lconfig'

    at Function.Module._resolveFilename (module.js:338:15)

    at Function.Module._load (module.js:280:25)

    at Module.require (module.js:362:17)

    at require (module.js:378:17)

    at Object.<anonymous> (/home/filip/hallway/hallwayd.js:16:15)

    at Module._compile (module.js:449:26)

    at Object.Module._extensions..js (module.js:467:10)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:312:12)

    at Module.runMain (module.js:492:10)

[filip mertens]

Yes this command seems to do a lot more

env SUPPRESS_TIMESTAMPS=1 NODE_PATH=lib node hallwayd.js workersup

Op dinsdag 19 februari 2013 19:24:05 UTC+1 schreef Kristján Pétursson het volgende:

Hi Filip,

[filip mertens]

this did it:env SUPPRESS_TIMESTAMPS=1 NODE_PATH=lib node hallwayd.js apihost workersup

brilliant!

Op dinsdag 19 februari 2013 19:24:05 UTC+1 schreef Kristján Pétursson het volgende:

Hi Filip,

[filip mertens]

thank you all!

Op dinsdag 19 februari 2013 20:22:10 UTC+1 schreef filip mertens het volgende:

[Kristján Pétursson]

Glad to hear it!

The important part of that command is the `NODE_PATH=lib`, which tells node where to look for Hallway modules like lconfig - same way the PATH environment variable does in your shell.

Happy Hacking!

Kristján