IRC logs for #farmOS, 2017-03-28 (GMT)

2017-03-27
2017-03-29
TimeNickMessage
[20:47:25]<lazerorca>thank you soooo much for your help
[22:06:03]* itnomad has joined #farmos
[22:19:30]<itnomad>Hello. Docker is pretty cool. I took a couple of days to familiarize myself with it. Nice to not be messing with drush, or compose, or the version problems.
[22:20:34]<itnomad>I got the image and on running it connected to the web site where the drupal installation is running. I'm having trouble with the database setup.
[22:21:45]<itnomad>I'm following these instructions. farmos.org/development/docker/
[22:24:05]<itnomad>It's tricky. I'm using docker in a Centos7 virtual machine hosted on a Fedora 25 computer. I created the database on the Centos7 virtual machine and I wonder if I should be creating it on the farmos container or something like that.
[22:25:59]<itnomad>Maybe easier just to get a Centos 7 cloud server and set things up there. I have a couple of cloudservers with Cloudatcost, but they have been a lot of trouble to work with. So they sit idle.
[22:34:07]* JustTB has quit (Quit: Leaving.)
[23:12:12]<itnomad>I think I just found what I need in your documentation. There is a MariaDB database container available on the host system.
[23:12:43]<itnomad>Outstanding! You guys have really done some great work with this.
[23:12:54]<itnomad>Bedtime now.
[23:12:57]* itnomad has quit (Quit: Leaving)
[05:08:01]* JustTB has joined #farmos
[05:14:45]* JustTB has quit (Quit: Leaving.)
[05:42:27]* JustTB has joined #farmos
[06:04:48]* M-DzzzzzzR has quit (Write error: Connection reset by peer)
[06:19:46]* M-DzzzzzzR has joined #farmos
[08:20:37]* Don has joined #farmos
[08:20:59]<Don>I could not get my map to work,
[08:21:00]* Don is now known as Guest4077
[08:21:19]<Guest4077>i followed instruction on the drupal page...
[08:22:20]<mstenta>Hi Don
[08:22:28]<mstenta>Guest4077 ^
[08:22:46]<mstenta>What is the issue you're seeing?
[08:23:08]<Guest4077>Oh, i just fixed it
[08:23:16]<mstenta>Great! :-)
[08:23:46]<Guest4077>the map was initially disappearing, then i just see the source options, the help page said option, was not looking at source option
[08:24:19]<Guest4077>Thanks Mstenta, i can see your help on all the pages, and you are even responding here...
[08:25:11]<mstenta>Guest4077: sure thing! glad you figured it out!
[08:25:48]<mstenta>Eventually I'd like to add an option during the farmOS installation for you to enter the API key, and then connect the dots in the background - to make this easier
[08:26:08]<mstenta>And/or also have the ability to choose a different default map source (not Google)
[08:26:23]<mstenta>Most require API keys these days, though, so the problem will be the same.
[08:31:41]<mstenta>Guest4077: if you start using farmOS regularly, consider adding your farm to http://farmOS.org/community/farms !
[08:31:47]<Guest4077>That is a great idea, so they can get it running from the get go...For now, if you had written, click the source option link to add the API key, i would have finished like 5mins..
[08:31:47]<mstenta>Looking to grow that list... :-)
[08:32:16]<Guest4077>Ok...great, i might write a blog on this since i have a tech blog.
[08:32:34]<mstenta>Guest4077: oh ok... i can update that... are you referring to this page? v
[08:32:38]<mstenta>https://www.drupal.org/node/2768895
[08:32:58]<Guest4077>yes...
[08:32:58]<mstenta>Guest4077: awesome! let me know if you do and i'll put a link on http://farmOS.org/community/press !
[08:33:00]<mstenta>:-)
[08:33:19]<Guest4077>admin/structure/openlayers/sources/list/farm_map_source_google_hybrid/edit/options ....just add source options, and Baaaam...it is way easier...
[08:33:34]<Guest4077>ok, i will save this now, and get back to you
[08:34:36]<mstenta>Guest4077: should i reword step 4 on this page? https://www.drupal.org/node/2768895
[08:34:45]<mstenta>is that what you mean?
[08:36:05]<Guest4077>yes, please
[08:37:08]<mstenta>Guest4077: what do you think i should change it to?
[08:37:10]<Guest4077>At administrative settings, click on the "source options" link to enter the API key
[08:37:41]<Guest4077>At administrative settings, click on the "Source type options" link to enter the API key..
[08:37:59]<mstenta>Oh... but doesn't that link take you directly there? (admin/structure/openlayers/sources/list/farm_map_source_google_hybrid/edit/options)
[08:39:57]<mstenta>I figured it was easier to just provide the direct link to that page than to try to explain how to get there through the UI
[08:41:21]<Guest4077>ohh, i will see
[08:41:52]<Guest4077>Ohhhh, you were right
[08:42:01]<Guest4077>i was following the UI...OMG..
[08:42:03]<mstenta>Oh ok great! :-)
[08:42:22]<mstenta>Ah yea... it is definitely tricky to find it in the UI if you are new to the Openlayers module
[08:42:22]<Guest4077>i was following links, so i missed that, ok...t
[08:42:24]<Guest4077>thanks once again
[08:42:32]<mstenta>You're welcome!
[08:42:46]<mstenta>I'm impressed you found it without the link!
[08:42:49]<mstenta>:-)
[08:43:50]<Guest4077>:)
[08:46:11]* Guest4077 has quit (Quit: Page closed)
[09:56:11]* JustTB has quit (Quit: Leaving.)
[09:59:10]* JustTB has joined #farmos
[13:05:18]* itnomad has joined #farmos
[14:34:44]<mstenta>hi itnomad - did you get it all working with docker?
[14:38:44]<itnomad>I'm being pulled in several directions today. Now, I'm following the instructions you suggested, carefully. I just ran docker-compose up. Funny the program could not be found when run with sudo. After an 'su' though, no problem.
[14:41:00]<mstenta>itnomad: i should mention - i've only tested this myself on ubuntu 16.04
[14:41:27]<itnomad>docker-compose finished. There is an error. Could not start the www service.
[14:41:33]<mstenta>not sure why it doesn't work with sudo... sounds like a path issue?
[14:41:40]<mstenta>hmm ok...
[14:41:48]<mstenta>do you have anything else running on port 80, perchance?
[14:42:05]<mstenta>(some other folks have run into an issue on Macs, which have Apache installed by default)
[14:42:26]<mstenta>if so, you can tweak your docker-compose.yml file to make farmOS/docker run on a different port
[14:42:29]<mstenta>ie: port 81
[14:43:39]<itnomad>apache is installed and I believe the service is called httpd not www.
[14:44:17]<mstenta>ok
[14:44:22]<itnomad>I'm going to dig around a little and check back in later. I've got some pressing matters to attend to.
[14:44:30]<mstenta>ok good luck!
[14:44:42]<mstenta>i'll put a few ideas into chat as i think of them...
[14:44:49]<mstenta>feel free to read at your liesure
[14:44:53]<mstenta>leisure*
[14:45:00]<itnomad>Thanks. Later. :)
[14:46:37]<mstenta>in the docker-compose.yml file, you'll see the "www" service and a "ports" attribute set to "80:80"
[14:47:01]<mstenta>that basically means: when you create this container (which we have decided to call "www"), map port 80 in the container to port 80 on the host
[14:47:27]<mstenta>so when a request to port 80 hits your host server (Centos?) then it is forwarded to port 80 of the container
[14:47:54]<mstenta>at that point (in the container), our docker image has Apache listening on port 80, so it picks it up, processes it (through Drupal/farmOS) and gives you back the page
[14:48:17]<mstenta>so... if you are ALREADY running Apache on your host system, then port 80 is already taken
[14:48:31]<mstenta>in that case, you can either: a) turn off Apache on your host (if you don't need it)
[14:49:00]<mstenta>or b) change the "ports" in docker-compose.yml to something like "81:80"
[14:49:14]<mstenta>which says "take any requests on the host's port 81 and forward them to port 80 in the container"
[14:49:48]<mstenta>then try docker-compose up again, and hopefully the www service is able to start
[14:50:04]<mstenta>if it does, then you can view your farmOS site at http://127.0.0.1:81
[14:50:14]<mstenta>(note the port at the end ":81")
[14:50:35]<mstenta>hope that all makes sense! and feel free to ignore if any of that was already obvious to you :-)
[16:55:35]<itnomad>when I ran 'docker-compose up' I got a lot of permissions errors. First on reading the /var/lib/mysql and then on creating all the directories the script tries to create.
[16:56:08]<mstenta>itnomad: docker-compose needs to be run as sudo too i believe
[16:56:29]<mstenta>that might be the issue... ?
[16:57:25]<mstenta>what that before or after the port 80 issue you had earlier?
[16:57:44]<itnomad>I ran it after switching to root. I don't understand why using sudo is acting differently that running as root.
[16:59:08]<itnomad>Maybe I'll download and install ubuntu 16.04. I'm not really tied to Centos, it's just what I'm most familiar with.
[17:00:30]<mstenta>hmm yea i'm not sure either
[17:00:33]<itnomad>Under sudo, docker-compose: command not found. Very odd.
[17:00:45]<mstenta>it does sound like there is some subtle difference in the way sudo works on centos vs ubuntu...
[17:01:22]<mstenta>or maybe it's just an issue with paths... ie: the directory that docker is installed in is not in the path for your user?
[17:03:34]<mstenta>but if you're open to trying ubuntu i say do that!
[17:03:35]<itnomad>/usr/local/bin is most certainly in my user's path.
[17:03:41]<mstenta>hmm
[17:03:52]<mstenta>yea i would have been surprised if it wasn't...
[17:04:16]<mstenta>where is docker and docker-compose installed?
[17:04:21]<mstenta>in mine, docker is in /usr/bin
[17:04:32]<mstenta>docker-compose is in /usr/local/bin
[17:06:49]<itnomad>docker-compose is owned by root.root and is in /usr/local/bin
[17:07:01]<itnomad>same here. docker is in /usr/bin
[17:07:14]<mstenta>hmm yea i'm not sure why it's not working
[17:07:28]<mstenta>if you run "docker" without sudo, does it also say not found?
[17:08:43]<mstenta>hmm... doing some googling... http://stackoverflow.com/questions/30379381/docker-command-not-found-eve...
[17:08:56]<mstenta>could it be that you installed that instead of the real docker?
[17:09:18]<mstenta>did you install using the centos package manager? or from the instructions on docker.com?
[17:09:53]<mstenta>or wait... nevermind... you said before that it almost worked (with "could not start www service") - so that would suggest you have docker
[17:10:06]<mstenta>what do you get when you run "docker --version" and "docker-compose --version" ?
[17:10:39]<itnomad>Interesting. If I run $docker, I get a usage error. If I run $docker images, the program is not found
[17:10:51]<itnomad>okay trying your last suggestion.
[17:12:20]<itnomad>I get docker version 1.12.6 and docker-compose version 1.12.0-rc2
[17:13:36]<itnomad>I'm being pulled away again. I'll be back later.
[17:14:47]<mstenta>hmm ok...
[17:15:38]<mstenta>the current version of docker is 17.03.0-ce - https://github.com/docker/docker/blob/master/CHANGELOG.md
[17:16:26]<mstenta>(after 1.13.1 they changes to the 17.x.y numbering (where 17 is the year, x is the month))
[17:16:36]<mstenta>so your version is a little old... but not that bad... it should still work
[17:16:51]<mstenta>the docker-compose version is a little more confusing...
[17:16:58]<mstenta>because the latest version is 1.11.0 - https://github.com/docker/compose/blob/master/CHANGELOG.md
[17:17:09]<mstenta>are you sure yours is 1.12.0-rc2?