*** gvincent has joined #ara | 06:20 | |
gvincent | code . | 06:22 |
---|---|---|
*** itxaka_ has joined #ara | 09:20 | |
*** altlogbot_2 has quit IRC | 09:24 | |
*** altlogbot_2 has joined #ara | 09:24 | |
*** itxaka_ has quit IRC | 10:08 | |
*** dbpiv has joined #ara | 12:48 | |
*** etienne has joined #ara | 15:04 | |
*** itxaka_ has joined #ara | 15:47 | |
*** itxaka_ has quit IRC | 17:34 | |
ara-slack | julian.daly: Hallo: What should I take as the definitive steps to get ARA working on a clean CentOS7 VM ? only https://ara.readthedocs.io/en/latest/installation.html ? | 17:50 |
dmsimard | @julian.daly: you'd need to install the python36 interpreter from EPEL first | 17:57 |
dmsimard | since centos7 doesn't come with py3 out of the box | 17:57 |
ara-slack | julian.daly: On a reasonably clean debian I get after running "~/.ara/virtualenv/bin/pip install ara[server]" no indication that ara is running. | 18:00 |
ara-slack | julian.daly: I run the next step, from source, but when I run "pip install ./ara-src[server]" I get "File "/usr/bin/pip", line 9, in <module>" "from pip import main" | 18:02 |
ara-slack | julian.daly: How can I get it working on a Server rather than just 127.0.0.1 ie I would like it to work at a set IP such as 10.20.2.2. This should be possible right? | 18:04 |
dmsimard | @julian.daly: installing ara doesn't make it run, it just installs the code and the dependencies -- after installing it, you need to tell Ansible to use it and then data will be recorded (locally in a sqlite database by default) | 18:08 |
dmsimard | Launching the server without bells and whistles is just "ara-manage runserver" or "ara-manage runserver x.x.x.x:port" for it to listen on a different address or port | 18:08 |
dmsimard | So for example you could do "ara-manage runserver 0.0.0.0:8000" to make it listen on all interfaces | 18:09 |
dmsimard | but then, if you want to browse the server through something like http://10.20.2.2:8000, you'll probably need to add 10.20.2.2 to the ALLOWED_HOSTS configuration | 18:10 |
dmsimard | so, then it becomes something like: 1) export ARA_ALLOWED_HOSTS="['10.20.2.2','localhost']" 2) ara-manage runserver 0.0.0.0:8000 | 18:10 |
dmsimard | the defaults for allowed_hosts are in ~/.ara/server/settings.yaml -- you can edit that so you don't need to export the variable. | 18:11 |
ara-slack | julian.daly: ara-manage runserver 0.0.0.0:8000 gives me "usage: ara-manage [-?] {db,runserver,createall,dropall,shell} ... " " ara-manage: error: too many arguments " | 18:29 |
ara-slack | julian.daly: " * Serving Flask app "ara" (lazy loading) " " * Environment: production " " WARNING: Do not use the development server in a production environment. "--Why? "Use a production WSGI server instead." --such as what,django? | 18:31 |
dmsimard | @julian.daly: ara 0.16.x is based on Flask and runs both py2 and py3 while 1.x runs on Django on py3 -- if you installed from a python2 interpreter, you might have picked up the latest version of 0.16 | 18:33 |
*** itxaka_ has joined #ara | 18:47 | |
ara-slack | julian.daly: ok. I cannot see which version I have. How can I find this out ? | 18:57 |
ara-slack | julian.daly: python --version gives me " Python 2.7.13 " | 18:57 |
*** itxaka_ has quit IRC | 19:12 | |
*** Daemoen_ is now known as Daemoen | 19:14 | |
*** etienne has quit IRC | 23:03 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!