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.
[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!!!**
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?
"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
[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)
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
[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] 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.
@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.