Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 04 2017 13:34
    benmag1 opened #762
  • Sep 16 2016 02:55
    coveralls commented #663
  • Feb 02 2016 14:42

    itayw on gh-pages

    trying to route joolajs to joo.… (compare)

  • Feb 02 2016 14:24

    itayw on gh-pages

    trying to route joolajs to joo.… (compare)

  • Jan 09 2016 16:12
    avif opened #761
  • Jan 05 2016 10:06
    avif commented #760
  • Jan 05 2016 09:57
    itayw labeled #760
  • Jan 05 2016 09:56
    itayw assigned #760
  • Jan 05 2016 09:56
    itayw commented #760
  • Jan 04 2016 18:08
    avif opened #760
  • Dec 31 2015 08:38

    itayw on develop

    removed zookeeper from travis (compare)

  • Dec 30 2015 14:15

    itayw on v0.8.18

    (compare)

  • Dec 30 2015 14:15

    itayw on develop

    updated pre/post publish to upd… version bump 0.8.18 Finish v0.8.18 (compare)

  • Dec 30 2015 14:15

    itayw on master

    Finish v0.8.17 updated pre/post publish to upd… version bump 0.8.18 and 1 more (compare)

  • Dec 29 2015 08:09

    itayw on v0.8.17

    (compare)

  • Dec 29 2015 08:09

    itayw on develop

    version bump 0.8.17 Finish v0.8.17 (compare)

  • Dec 29 2015 08:09

    itayw on master

    Finish v0.8.16 #759 fixed issue with cloneexte… version bump 0.8.17 and 1 more (compare)

  • Dec 20 2015 21:07

    itayw on develop

    #759 fixed issue with cloneexte… (compare)

  • Dec 20 2015 21:07
    itayw opened #759
  • Dec 13 2015 19:00
    itayw labeled #758
Ivan Hamer
@ihamer
@itayw Hey thanks for the update. I tried it, but I cannot access http://localhost:8080.
My 'docker ps' shows which looks right:
2c9459e17819 joola/joola:latest "/usr/bin/supervisor 3 minutes ago Up 6 seconds 8081/tcp, 22/tcp, 0.0.0.0:8080->8080/tcp ecstatic_ardinghelli
however, when I try 'wget http://localhost:8080', I get:
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Browser shows similar message (reset...)
Ivan Hamer
@ihamer
Hmmm... 'ps aux' inside the container shows only three processes: supervisord, mongodb and sshd... is this right?
Itay Weinberger
@itayw
Hmmm indeed @ihamer :) you're missing joola in the process list, it probably started and died for some reason, there are specific logs within the docker container /opt/joola/bin/logs.
I've spent a few hours yesterday working on the vagrant and docker containers and might have broke something (the docker build is automated). I'm going to take a look in about an hour or so and I'll focus on clearing the both docker and vagrant as operational by the end of the day. thanks for your patience :)
Itay Weinberger
@itayw
@ihamer found the bug. Fix already deployed on branch containers/docker, waiting for docker hub to finish with build and push and I'll ping you when done.
Itay Weinberger
@itayw
@ihamer all ready for your check, here what I get:
itay@joola01:~$ sudo docker run -p 8080:8080 -p 222:22 -it joola/joola
/usr/lib/python2.7/dist-packages/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2015-02-18 08:47:40,458 CRIT Supervisor running as root (no user in config file)
2015-02-18 08:47:40,458 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2015-02-18 08:47:40,474 INFO RPC interface 'supervisor' initialized
2015-02-18 08:47:40,475 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-02-18 08:47:40,475 INFO supervisord started with pid 1
2015-02-18 08:47:41,477 INFO spawned: 'mongodb' with pid 8
2015-02-18 08:47:41,477 INFO spawned: 'sshd' with pid 9
2015-02-18 08:47:41,478 INFO spawned: 'joola' with pid 10
2015-02-18 08:47:43,204 INFO success: mongodb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-02-18 08:47:43,206 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-02-18 08:47:57,761 INFO exited: joola (exit status 0; not expected)
2015-02-18 08:47:58,763 INFO spawned: 'joola' with pid 21
2015-02-18 08:48:24,634 INFO success: joola entered RUNNING state, process has stayed up for > than 25 seconds (startsecs)
You'll notice that Joola starts twice, this is because during the first run MongoDB wasn't available, but the restart flag kicked in and it tried again and stayed up after MongoDB became available.
Also, you'll notice that I've used -p 222:22, this allows you to connect to the machine while it's running and get the logs for review. Here's an example:
itay@joola01:~$ ssh joola@localhost -p 222
joola@localhost's password: 
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.2.0-70-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

joola@cc7e323e50c2:~$ cd /opt/joola/logs
joola@cc7e323e50c2:/opt/joola/logs$ cat joola.log 
08:47:57.593Z  INFO joola: Skipping Redis store for configuration, running in stand-alone mode.
08:47:57.677Z  INFO joola: Initializing connection to provider [MongoDB].
undefined
undefined
[Error: failed to connect to [localhost:27017]]
08:47:57.757Z  WARN joola: Received exit signal: 0
08:47:57.757Z  WARN joola: Gracefully shutting down, code: 0
08:47:57.757Z  WARN joola: State for [core] changed to [stop]: received code [0]
08:48:14.338Z  INFO joola: Skipping Redis store for configuration, running in stand-alone mode.
08:48:14.441Z  INFO joola: Initializing connection to provider [MongoDB].
08:48:14.472Z  INFO joola: joola HTTP server listening on port [0.0.0.0:8080].
08:48:14.535Z  INFO joola: joola version 0.8.6 started [PdsejeNaTWxuRnHzE5STHiHHmOxWFmt4].
joola@cc7e323e50c2:/opt/joola/logs$
The password for joola is joola.
Let me know how it goes :)
Itay Weinberger
@itayw
great news, the coming merge of #673 will allow joola to run without a stack, i.e. no need for redis/mongo/rbq etc... Only if you need to scale up and support multiple nodes you'll need to configure these additional sources.
Ivan Hamer
@ihamer
It works! Great. I really appreciate such a quick response, Itay.
Also, great work to make it standalone.
Itay Weinberger
@itayw
@ihamer my pleasure, let me know if I can help further. I expect to complete docs, especially the needed SDK ones by the first week of March.
Omer Katz
@thedrow
@itayw Still waiting for OAuth instead of the current auth implementation...
Itay Weinberger
@itayw
hi @thedrow, yeah, sorry it dropped below radar. One thing I did struggle with is identifying how the OAuth part should work in combination with Joola. I must admit that I'm a bit lacking in this field.
Itay Weinberger
@itayw
I just merged #661 into the develop branch. Joola can now be executed without any stack, send me your feedback :)
Omer Katz
@thedrow
@itayw Hi, so OAuth can be either used as a standalone auth mechanism or in order to integrate with other systems
For example, if I have my own SaaS which uses Joola I'd like to reuse the same OAuth token to identify the user both on Joola and on my app
It also means that your API will use a standard mechanism for authentication which makes implementing clients much easier
Itay Weinberger
@itayw
I just merged #661 into the develop branch. Joola can now be executed without any stack, send me your feedback :)
Omer Katz
@thedrow
@itayw If you have more questions I'd be happy to assist
Itay Weinberger
@itayw
@thedrow what would the flow for your SaaS example? who's generating the token and how does the exchange actually works in the setup you have in mind?
Omer Katz
@thedrow
The Authorization server generates the token
It can be Joola or someone else
Itay Weinberger
@itayw
@thedrow to be honest I think would be good to incorporate it into joola but i'm a bit fuzzy on the actual flow.
You provide a client id and secret key and get a token and a refresh token in exchange
Itay Weinberger
@itayw
checking....
Omer Katz
@thedrow
The whole idea is to be able to delegate the authentication and permissions to another service that already knows what a user can or can't view or edit
Itay Weinberger
@itayw
welcome @learnsomuch, feel free to ask questions :)
Sankar
@learnsomuch
Thank you @itayw .. I am Sankar who contacted you via facebook :-)
Itay Weinberger
@itayw
Ivan Shumkov
@Shumkov
Hello! For first, Joola is very similar that we are design now for internal analytics :)
We are think about move to trash our diagrams and start to using your great product!
Ivan Shumkov
@Shumkov
Can i ask you few questions to understand that?
Ivan Shumkov
@Shumkov

What's mean - "However, please note that Joola does not support query filters over arrays."?
I can't filter by array field?

For example:
i have interesets array field that contain ID's of user interests 1, 2 and 3.
Can i query users with 1 and 2 interests' IDs?

Itay Weinberger
@itayw
Hi @shumkov, I'm happy to hear you like Joola :)
With regards to in array queries, we have limited support, but I need to look into it and see how we can achieve your speicifc requirements.
I'll give it some tests tomorrow and let you know what I find.
Itay Weinberger
@itayw
@Shumkov I opened a ticket for adding tests, if you wish to follow it:joola/joola#700
Ivan Shumkov
@Shumkov
Thanks
I saw elasticsearch store adapter and i'm cunfused
For each insert you try to create index. Two query per one document.
Why did you not using bulk insert?
Did you use elasticsearch store in production with big data?
Itay Weinberger
@itayw
Were using
We're using mongo in production, the elastic plugin is still under heavy development
There are several performance/efficiency issues with the plugin at the moment. For example each insert also calls for an index refresh which is not performance friendly.
Ivan Shumkov
@Shumkov
Yes, i told you the same.
Itay Weinberger
@itayw
@Shumkov i've worked on the es plugin and took care of some of the major issues. In addition I've added examples to #700 showing in-array queries. It's not stable yet and I do expect to apply several additional changes to the plugin, but let me know what you think. Builds are now running through travis, so make sure you try out develop branch. If you want I can also push a pre-release to npm.