These are chat archives for ushahidi/Community

4th
Nov 2016
Stephanie Liu
@sanqianliusi
Nov 04 2016 00:05
I want to ask the last question:could you please give me all the version you used ?php..apache....,all the stuff.
Cam Macdonell
@cmacdonell
Nov 04 2016 05:11
Hi, I'm trying to launch a platform-client using docker. I tried the commands in the README.md, but they just give a vanilla NGINX server installation. I noticed there are number of other docker configurations. I built a docker image using the build.Dockerfile and it works, but I'm unsure how to proceed.
Kyoungrok Jang
@kyoungrok0517
Nov 04 2016 07:54
I'm using platform-release v3.6.1. It's strange I couldn't save the General settings. Did anyone report the same thing?
Ushbot
@ushbot
Nov 04 2016 07:59
[Robbie Mackay, Ushahidi] @cmacdonell the docker configs in platform-client are used for our CI, rather than development. That said I think @davidlosada might have been using one of them, or something very similar for dev.. he might be able to give you some direction
[Robbie Mackay, Ushahidi] Looking at the README.md .. those are very old instructions I should have long since removed. Sorry.
[Angela Oduor Lungati, Ushahidi] **waves at Cam!!!**
Liwei
@willis50317
Nov 04 2016 08:46
hello,
I have already successfully launch a local ushahidi website on http://localhost:8080.
Then, I turn off the vm and try to follow the same progress to launch another revised version.
After completing "vagrant up && vagrant provision" for "platform" and "gulp" for "platform-client", why this time I can not access http://localhost:8080?
blob
"ushahidi-platform-openisdm" is the one I launch for the revised version.
You can see I actually turn off the "ushahidi-platform" which I ran for the official version.
Is it because of some conflict on port 8080?
Please, help me to figure out the problem. Thanks
Liwei
@willis50317
Nov 04 2016 08:54
blob
Stephanie Liu
@sanqianliusi
Nov 04 2016 10:48
Sorry to come back to trouble you
2016-11-04 18:48:43屏幕截图.png
Any Idea about this?
@willis50317 @ushbot
Ushbot
@ushbot
Nov 04 2016 11:33
[David Losada, Ushahidi] willis, if there are port number conflicts, vagrant will tell you when starting the vm
[David Losada, Ushahidi] sanqian, first step would probably to make sure you’ve got the necessary php extensions installed, those are listed in the manual
[David Losada, Ushahidi] > The following php extensions enabled: curl, gd, imap, json, mcrypt, mysqlnd (optional)
Stephanie Liu
@sanqianliusi
Nov 04 2016 11:35
I got them then the error narrow to imap only
2016-11-04 19:35:40屏幕截图.png
I do apt-get install php5-imap
[David Losada, Ushahidi] cmacdonell, there is no container configuration in platform-client pre-packaged for running right now, but it would be fairly straightforward to extend/modify either test.Dockerfile or run.Dockerfile and the associated script in order to accomplish that
[David Losada, Ushahidi] the idea is pretty much to set up everything just as it’s done now, but run “gulp watch” at the end (instead of tests or build process)
Stephanie Liu
@sanqianliusi
Nov 04 2016 11:41
Cannot create cache directory /home/ss/.composer/cache/repo/https---packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /home/ss/.composer/cache/files/, or directory is not writable. Proceeding without cache
Does that matter?
Ushbot
@ushbot
Nov 04 2016 11:46
[David Losada, Ushahidi] looks like a case of running once with sudo
[David Losada, Ushahidi] which means that you have to keep using sudo in subsequent invocations
[David Losada, Ushahidi] (for composer or bin/update)
Stephanie Liu
@sanqianliusi
Nov 04 2016 11:58
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.
Package league/url is abandoned, you should avoid using it. Use league/uri instead.
Does that matter?
Can I ignore it?
Ushbot
@ushbot
Nov 04 2016 11:59
[David Losada, Ushahidi] it’s ok
Stephanie Liu
@sanqianliusi
Nov 04 2016 12:11
2016-11-04 20:09:40屏幕截图.png
I can only use nodejs v6
or other version is tolerrable
Ushbot
@ushbot
Nov 04 2016 12:12
[David Losada, Ushahidi] v5 could work
Stephanie Liu
@sanqianliusi
Nov 04 2016 12:14
ss@ss-All-Series:~/platform$ nodejs -v
v0.10.25
that one is not ok,right?
Ushbot
@ushbot
Nov 04 2016 12:15
[David Losada, Ushahidi] it may work.. it may not
[David Losada, Ushahidi] we recently dropped support for v0.10
Stephanie Liu
@sanqianliusi
Nov 04 2016 12:30
if you're getting set up for development, you might want to fork the repository first.
what does that mean?
Ushbot
@ushbot
Nov 04 2016 12:30
[David Losada, Ushahidi] that’s only if you plan to make changes to the code
[David Losada, Ushahidi] this is what forking means: https://help.github.com/articles/fork-a-repo/
Liwei
@willis50317
Nov 04 2016 12:43
well... I didn't see anything wrong when I ran "vagrant up && provision"
oh if I run "gulp node-server", I can successfully access "localhost:8080".
Do you know why it work but "gulp" didn't?
haha it's always great to meet you David!
Ushbot
@ushbot
Nov 04 2016 13:13
[David Losada, Ushahidi] willis, looking at the latest version, the default task in gulp is to build the frontend assets, and keep watching for any changes in the source to trigger a rebuild. However, that doesn’t bring up a server to serve those assets to a browser. That’s exactly what node-server does.
[David Losada, Ushahidi] glad to assist :)
Liwei
@willis50317
Nov 04 2016 13:21
well... but why at the first time I only need to run "gulp" and then I could access "localhost:8080"?
Ushbot
@ushbot
Nov 04 2016 13:21
[David Losada, Ushahidi] I’m not really sure, it may be running a slightly older version? We may have modified the layout of the gulp tasks recently
Liwei
@willis50317
Nov 04 2016 13:24
oh you mean the official version I ran is a old version? and for the new version, we should run both "gulp" and "gulp node-sever" to access "localhost:8080" on browser?
Ushbot
@ushbot
Nov 04 2016 13:26
[David Losada, Ushahidi] I would need to look into what has changed. As of today’s version, gulp node-server also seems to be doing file monitoring and building , so you shouldn’t need to keep both tasks running. From gulpfile.js:
/**
 * Task: `node-server`
 * Runs a simple node connect server and runs live reloading.
 */
Stephanie Liu
@sanqianliusi
Nov 04 2016 13:27
2016-11-04 21:26:55屏幕截图.png
How about this errors?
Ushbot
@ushbot
Nov 04 2016 13:28
[David Losada, Ushahidi] it seems to be because of a corrupted or interrupted download
Stephanie Liu
@sanqianliusi
Nov 04 2016 14:32
how can I fix it?
it still happen
after one hour
Ushbot
@ushbot
Nov 04 2016 14:39
[David Losada, Ushahidi] maybe try removing it first with “sudo npm cache clean ushahidi-platform-library"
[David Losada, Ushahidi] it’s hard to tell how many times you will need to try the download until it succeeds ..
[David Losada, Ushahidi] I’ve checked on my side and it works fine for us
Stephanie Liu
@sanqianliusi
Nov 04 2016 14:40
ok,thank you .
firewall is too strong
for us to download something
thank you for you help
[David Losada, Ushahidi] sorry about those firewall problems
Stephanie Liu
@sanqianliusi
Nov 04 2016 15:01
2016-11-04 23:00:51屏幕截图.png
new errors~~
Ushbot
@ushbot
Nov 04 2016 15:23
[David Losada, Ushahidi] it’s not really clear what happened there. phantomjs carries a big download too. any other error messages when you scroll up?
Cam Macdonell
@cmacdonell
Nov 04 2016 15:35
@rjmackay No sweat, the Dockerfile files have a dev's name in them who I know hasn't been involved in a while, so I didn't put too much hope or time in them. I'll go with a VM instead of docker, unless someone has a dockerfile ready to go.
waves back at @aoduor :)