@itayw Remember that we talked about using a service discovery tool that doesn't require you to do weird things with a broker? https://github.com/PearsonEducation/thalassa-consul
That project might help
We've introduced many new features and advantages to Joola, let me know if you need a hand.
Hi all, we started working on an ElasticSearch data plugin. Check it out here: https://github.com/joola/joola.datastore-elasticsearch
Let us know of any feedback.
I've scheduled it to the first Monday of March.
Hi. I've been trying to run the docker demo app, with no success... After starting the container, I try: root@9bf06234cf9b:/# curl -i -k https://127.0.0.1:8081/system/version?APIToken=apitoken-demo
and get:
curl: (7) Failed to connect to 127.0.0.1 port 8081: Connection refused
and get:
curl: (7) Failed to connect to 127.0.0.1 port 8081: Connection refused
when you run your docker container next time, please use port 8080 instead of 8081, I suspect the error you experienced is due to an SSL certificate issue. You can find updated instructions in https://registry.hub.docker.com/u/joola/joola/
@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...)
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...)
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 :)
@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 :)
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
It can be Joola or someone else
You provide a client id and secret key and get a token and a refresh token in exchange