Git Product home page Git Product logo

platform-release's Introduction

Ushahidi Platform version 6 releases

Install and run the Ushahidi Platform easily. No builds, no compiling.

The Ushahidi platform is currently composed of two components:

Installation instructions

Proceed to download a releases available in the "Releases" tab of this repository. That will contain all the files necessary for running our software. The included README.release.md file will contain more specific instructions for installation.

Run with Docker

This is an easy way to get started and get a fairly stable service running.

Requirements are docker-engine and docker-compose.

Just run docker-compose up , the Ushahidi platform will be available at port 80 of your docker engine host. Default credentials: [email protected] / admin (do change these for any installation you plan to have exposed)

Versions of the software will be automatically downloaded for you, based on the contents of build_env.sh

Step 1: Clone the Repo

git clone https://github.com/ushahidi/platform-release.git

Step2 : Change to Ushahidi platform release directory

cd platform-release/

Step3: Run docker-compose

docker-compose up

Docker: Backups

Run ./do_backup.sh on this folder to make a backup of your database and uploaded files.

Docker: SSL/TLS

  1. You will need a folder with your certificates, and this should be mounted as a volume in your pertinent container.

  2. You will need a properly configured web server.

The configuration for the web servers is found under the dist/ folder and you may modify it in order to enable TLS and point at your certificate files.

However, a secure TLS configuration actually requires you to get a number of things right. Because of this, we rather prefer the approach of using a known well maintained implementation and configuration.

Our current suggestion to run a SSL/TLS docker setup is with the very excellent jwilder/nginx-proxy container.

You will find an example of usage of nginx-proxy in the docker-compose.tls.yml file. In order to make that example work for you, please adjust a couple things:

  • Change the occurrences of 127.0.0.1.xip.io for the hostname URL that you will use to publish your Ushahidi deployment.

  • Ensure your certificates are in the tls-certs/ folder, using the proper naming conventions. i.e. if your publishing URL is ushahidi.example.com , you will need to have ushahidi.example.com.crt and ushahidi.example.com.key files.

Also note that you will need to run docker-compose -f docker-compose.tls.yml ... rest of the command ..., instead of plain docker-compose, or set the the COMPOSE_FILE environment variable to docker-compose.tls.yml.

Docker: SSL/TLS with Let's Encrypt

This should be fairly doable with a variation of the nginx-proxy approach described above.

Contributions welcome!

Docker: Connecting the mobile app

Please note that the mobile app relies on the contents of the config.json file in order to connect to the API backend.

In order to help the app find the backend, ensure that the key backend_url in the JSON file is set appropriately to the absolute public URL of your deployment (i.e. "backend_url": "https://example.deployment.com" )

If you are running the Docker container, you may set this variable using the SITE_URL environment variable. (In the default install the site URL is the backend URL).

Other documentation

For other documentation, please check out our Developer and Contributor docs !

platform-release's People

Contributors

allamiro avatar angamanga avatar igunawan-sf avatar kethr-lee avatar lupa18 avatar rjmackay avatar rowasc avatar trendspotter avatar tuxpiper avatar ushahidlee avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

platform-release's Issues

Error migrations

./bin/phinx migrate -c application/phinx.php

Phinx by Rob Morgan - https://phinx.org. 0.8.0

using config file ./application/phinx.php
PHP Fatal error: Class 'Database_Mysqli' not found in /......../mapshow.ru/platform/vendor/ohanzee/database/src/Database.php on line 76
{
"errors": [
{
"status": "Fatal Error",
"title": "Class 'Database_Mysqli' not found",
"message": "Class 'Database_Mysqli' not found",
"class": "ErrorException",
"file": "/......./mapshow.ru/platform/vendor/ohanzee/database/src/Database.php",
"line": 76,
"trace": [
{
"function": "shutdown_handler",
"class": "Kohana_Core",
"type": "::",
"args": []
}
]
}
]

In a fresh install at release v3.10.0, the admin can't update any setting

I've completed the installation in a Ubuntu 16.04.4 server (PHP 7.0.28). At the first time logged in, the popup asked me to update email address. But I can't save it and with a 403 Forbidden response.

I tried to update the setting through database directly and clear the browser cache. Then the popup above no longer appeared. But then any time I want to save settings, it also give me a 403 Forbidden response even I'm using admin account.

I tried to read the response from /platform/api/v3/config and found all allowed_privileges only have read and search. Maybe by default, the admin should have the full privileges in the released installation?

docker-compose up on v4.0.0 causes the server to crash

Hi,

Ushahidi crashes when started via docker-compose. I used the tag v4.0.0 and changed the port to 2080.

Here's the relevant section of the logs:

$ dc logs -f ushahidi      
Attaching to platform-release_ushahidi_1
ushahidi_1  | + export PLATFORM_HOME=/var/www/html
ushahidi_1  | + PLATFORM_HOME=/var/www/html
ushahidi_1  | + export PLATFORM_API_HOME=/var/www/html/platform
ushahidi_1  | + PLATFORM_API_HOME=/var/www/html/platform
ushahidi_1  | ++ dirname /run.sh
ushahidi_1  | + . //build_env.sh
ushahidi_1  | ++ client_version=v4.0.0
ushahidi_1  | ++ api_version=v4.0.0
ushahidi_1  | ++ release_version=v4.0.0
ushahidi_1  | ++ client_url=
ushahidi_1  | ++ api_url=
ushahidi_1  | ++ client_tar=ushahidi-platform-client-bundle-v4.0.0.tar.gz
ushahidi_1  | ++ api_tar=ushahidi-platform-bundle-v4.0.0.tar.gz
ushahidi_1  | + [[ -z ushahidi-platform-client-bundle-v4.0.0.tar.gz ]]
ushahidi_1  | + [[ -z ushahidi-platform-bundle-v4.0.0.tar.gz ]]
ushahidi_1  | + '[' -z '' ']'
ushahidi_1  | + client_url=https://github.com/ushahidi/platform-client/releases/download/v4.0.0/ushahidi-platform-client-bundle-v4.0.0.tar.gz
ushahidi_1  | + '[' -z '' ']'
ushahidi_1  | + api_url=https://github.com/ushahidi/platform/releases/download/v4.0.0/ushahidi-platform-bundle-v4.0.0.tar.gz
ushahidi_1  | + release_target_folder=/tmp/release/ushahidi-platform-release-v4.0.0
ushahidi_1  | + case "$1" in
ushahidi_1  | + fetch
ushahidi_1  | + '[' '!' -d /tars ']'
ushahidi_1  | + '[' '!' -f /tars/ushahidi-platform-client-bundle-v4.0.0.tar.gz ']'
ushahidi_1  | + '[' '!' -f /tars/ushahidi-platform-bundle-v4.0.0.tar.gz ']'
ushahidi_1  | + build
ushahidi_1  | + mkdir -p /tmp/client
ushahidi_1  | + tar -C /tmp/client -xz -f /tars/ushahidi-platform-client-bundle-v4.0.0.tar.gz
ushahidi_1  | + mkdir -p /tmp/api
ushahidi_1  | + tar -C /tmp/api -xz -f /tars/ushahidi-platform-bundle-v4.0.0.tar.gz
ushahidi_1  | 
ushahidi_1  | gzip: stdin: unexpected end of file
ushahidi_1  | tar: Unexpected EOF in archive
ushahidi_1  | tar: Unexpected EOF in archive
ushahidi_1  | tar: Error is not recoverable: exiting now
platform-release_ushahidi_1 exited with code 2

Here's a complete log that includes the image build if you'd like to dig in further. But I'll edit the post to remove it if you think it is unnecessary.

$ docker-compose up --build
Creating network "platform-release_default" with the default driver
Building mysql
Step 1/8 : FROM alpine:3.5
 ---> f80194ae2e0c
Step 2/8 : MAINTAINER David Losada Carballo "[email protected]"
 ---> Running in bcea2dd69344
Removing intermediate container bcea2dd69344
 ---> 1cc1eae83149
Step 3/8 : RUN apk update &&     apk add mysql mysql-client &&     rm -rf /var/cache/apk/*
 ---> Running in 7c3150bcabb9
fetch http://dl-cdn.alpinelinux.org/alpine/v3.5/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.5/community/x86_64/APKINDEX.tar.gz
v3.5.3-40-g389d0b359a [http://dl-cdn.alpinelinux.org/alpine/v3.5/main]
v3.5.3-40-g389d0b359a [http://dl-cdn.alpinelinux.org/alpine/v3.5/community]
OK: 7963 distinct packages available
(1/11) Installing mariadb-common (10.1.32-r0)
(2/11) Installing libaio (0.3.110-r0)
(3/11) Installing ncurses-terminfo-base (6.0_p20171125-r1)
(4/11) Installing ncurses-terminfo (6.0_p20171125-r1)
(5/11) Installing ncurses-libs (6.0_p20171125-r1)
(6/11) Installing libgcc (6.2.1-r1)
(7/11) Installing libstdc++ (6.2.1-r1)
(8/11) Installing mariadb (10.1.32-r0)
Executing mariadb-10.1.32-r0.pre-install
(9/11) Installing mysql (10.1.32-r0)
(10/11) Installing mariadb-client (10.1.32-r0)
(11/11) Installing mysql-client (10.1.32-r0)
Executing busybox-1.25.1-r2.trigger
OK: 196 MiB in 22 packages
Removing intermediate container 7c3150bcabb9
 ---> 2124e883b365
Step 4/8 : COPY my.cnf /etc/mysql/my.cnf
 ---> 9614519de35c
Step 5/8 : COPY run.sh /etc/mysql/run.sh
 ---> cadf16182755
Step 6/8 : RUN mkdir /run/mysqld
 ---> Running in 8890d79d913b
Removing intermediate container 8890d79d913b
 ---> ba1a29e01b59
Step 7/8 : EXPOSE 3306
 ---> Running in 88c0921fd678
Removing intermediate container 88c0921fd678
 ---> 689cbecf8d13
Step 8/8 : CMD [ "/bin/sh", "/etc/mysql/run.sh" ]
 ---> Running in 08647640b860
Removing intermediate container 08647640b860
 ---> f0584023c920
Successfully built f0584023c920
Successfully tagged platform-release_mysql:latest
Building ushahidi
Step 1/8 : FROM ushahidi/php-fpm-nginx:php-7.0
 ---> 34af64346f31
Step 2/8 : WORKDIR /var/www
 ---> Running in cfbb26d0f5f9
Removing intermediate container cfbb26d0f5f9
 ---> 20ea5effa5e8
Step 3/8 : RUN apt-get update && apt-get install -y       unzip       rsync       netcat-openbsd       supervisor       cron       git &&     apt-get clean &&     rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
 ---> Running in 2054bf3f732c
Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:3 http://deb.debian.org/debian stretch Release [118 kB]
Get:4 http://security.debian.org stretch/updates InRelease [94.3 kB]
Get:5 http://security.debian.org stretch/updates/main amd64 Packages [626 kB]
Get:6 http://deb.debian.org/debian stretch-updates/main amd64 Packages [33.3 kB]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2434 B]
Get:8 https://packages.sury.org/php stretch InRelease [6760 B]
Ign:8 https://packages.sury.org/php stretch InRelease
Get:9 http://deb.debian.org/debian stretch/main amd64 Packages [9475 kB]
Get:10 https://packages.sury.org/php stretch/main amd64 Packages [125 kB]
Fetched 10.6 MB in 8s (1309 kB/s)
Reading package lists...
W: GPG error: https://packages.sury.org/php stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
W: The repository 'https://packages.sury.org/php stretch InRelease' is not signed.
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.11.0-3+deb9u4).
The following additional packages will be installed:
  exim4 exim4-base exim4-config exim4-daemon-light guile-2.0-libs libfribidi0
  libgc1c2 libgsasl7 libkyotocabinet16v5 liblzo2-2 libmailutils5
  libmariadbclient18 libntlm0 libpython-stdlib libpython2.7
  libpython2.7-minimal libpython2.7-stdlib libwrap0 mailutils mailutils-common
  mysql-common python python-meld3 python-minimal python-pkg-resources
  python2.7 python2.7-minimal tcpd
Suggested packages:
  anacron logrotate checksecurity eximon4 exim4-doc-html | exim4-doc-info file
  spf-tools-perl swaks mailutils-mh mailutils-doc python-doc python-tk
  python-setuptools python2.7-doc binutils binfmt-support openssh-client
  openssh-server supervisor-doc zip
The following NEW packages will be installed:
  cron exim4 exim4-base exim4-config exim4-daemon-light guile-2.0-libs
  libfribidi0 libgc1c2 libgsasl7 libkyotocabinet16v5 liblzo2-2 libmailutils5
  libmariadbclient18 libntlm0 libpython-stdlib libpython2.7
  libpython2.7-minimal libpython2.7-stdlib libwrap0 mailutils mailutils-common
  mysql-common netcat-openbsd python python-meld3 python-minimal
  python-pkg-resources python2.7 python2.7-minimal supervisor tcpd
The following packages will be upgraded:
  rsync unzip
2 upgraded, 31 newly installed, 0 to remove and 50 not upgraded.
Need to get 14.4 MB of archives.
After this operation, 50.5 MB of additional disk space will be used.
Get:1 http://security.debian.org stretch/updates/main amd64 exim4-config all 4.89-2+deb9u5 [377 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 cron amd64 3.0pl1-128+deb9u1 [95.4 kB]
Get:3 http://deb.debian.org/debian stretch/main amd64 libpython2.7-minimal amd64 2.7.13-2+deb9u3 [389 kB]
Get:4 http://deb.debian.org/debian stretch/main amd64 python2.7-minimal amd64 2.7.13-2+deb9u3 [1382 kB]
Get:5 http://security.debian.org stretch/updates/main amd64 exim4-base amd64 4.89-2+deb9u5 [1093 kB]
Get:6 http://deb.debian.org/debian stretch/main amd64 python-minimal amd64 2.7.13-2 [40.5 kB]
Get:7 http://deb.debian.org/debian stretch/main amd64 libpython2.7-stdlib amd64 2.7.13-2+deb9u3 [1897 kB]
Get:8 http://security.debian.org stretch/updates/main amd64 exim4-daemon-light amd64 4.89-2+deb9u5 [542 kB]
Get:9 http://deb.debian.org/debian stretch/main amd64 python2.7 amd64 2.7.13-2+deb9u3 [285 kB]
Get:10 http://deb.debian.org/debian stretch/main amd64 libpython-stdlib amd64 2.7.13-2 [20.0 kB]
Get:11 http://deb.debian.org/debian stretch/main amd64 python amd64 2.7.13-2 [154 kB]
Get:12 http://deb.debian.org/debian stretch/main amd64 libgc1c2 amd64 1:7.4.2-8 [208 kB]
Get:13 http://deb.debian.org/debian stretch/main amd64 libwrap0 amd64 7.6.q-26 [58.2 kB]
Get:14 http://deb.debian.org/debian stretch/main amd64 guile-2.0-libs amd64 2.0.13+1-4 [2232 kB]
Get:15 http://security.debian.org stretch/updates/main amd64 exim4 all 4.89-2+deb9u5 [7864 B]
Get:16 http://deb.debian.org/debian stretch/main amd64 libfribidi0 amd64 0.19.7-1+b1 [45.7 kB]
Get:17 http://deb.debian.org/debian stretch/main amd64 libntlm0 amd64 1.4-8 [20.9 kB]
Get:18 http://deb.debian.org/debian stretch/main amd64 libgsasl7 amd64 1.8.0-8+b2 [207 kB]
Get:19 http://deb.debian.org/debian stretch/main amd64 liblzo2-2 amd64 2.08-1.2+b2 [55.0 kB]
Get:20 http://deb.debian.org/debian stretch/main amd64 libkyotocabinet16v5 amd64 1.2.76-4.2+b1 [298 kB]
Get:21 http://deb.debian.org/debian stretch/main amd64 mailutils-common all 1:3.1.1-1 [642 kB]
Get:22 http://deb.debian.org/debian stretch/main amd64 mysql-common all 5.8+1.0.2 [5608 B]
Get:23 http://deb.debian.org/debian stretch/main amd64 libmariadbclient18 amd64 10.1.38-0+deb9u1 [785 kB]
Get:24 http://deb.debian.org/debian stretch/main amd64 libpython2.7 amd64 2.7.13-2+deb9u3 [1071 kB]
Get:25 http://deb.debian.org/debian stretch/main amd64 libmailutils5 amd64 1:3.1.1-1 [817 kB]
Get:26 http://deb.debian.org/debian stretch/main amd64 mailutils amd64 1:3.1.1-1 [573 kB]
Get:27 http://deb.debian.org/debian stretch/main amd64 netcat-openbsd amd64 1.130-3 [38.2 kB]
Get:28 http://deb.debian.org/debian stretch/main amd64 python-pkg-resources all 33.1.1-1 [166 kB]
Get:29 http://deb.debian.org/debian stretch/main amd64 rsync amd64 3.1.2-1+deb9u2 [393 kB]
Get:30 http://deb.debian.org/debian stretch/main amd64 tcpd amd64 7.6.q-26 [23.3 kB]
Get:31 http://deb.debian.org/debian stretch/main amd64 unzip amd64 6.0-21+deb9u1 [170 kB]
Get:32 http://deb.debian.org/debian stretch/main amd64 python-meld3 all 1.0.2-2 [37.3 kB]
Get:33 http://deb.debian.org/debian stretch/main amd64 supervisor all 3.3.1-1+deb9u1 [280 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 14.4 MB in 8s (1772 kB/s)
Selecting previously unselected package cron.
(Reading database ... 14172 files and directories currently installed.)
Preparing to unpack .../0-cron_3.0pl1-128+deb9u1_amd64.deb ...
Unpacking cron (3.0pl1-128+deb9u1) ...
Selecting previously unselected package libpython2.7-minimal:amd64.
Preparing to unpack .../1-libpython2.7-minimal_2.7.13-2+deb9u3_amd64.deb ...
Unpacking libpython2.7-minimal:amd64 (2.7.13-2+deb9u3) ...
Selecting previously unselected package python2.7-minimal.
Preparing to unpack .../2-python2.7-minimal_2.7.13-2+deb9u3_amd64.deb ...
Unpacking python2.7-minimal (2.7.13-2+deb9u3) ...
Selecting previously unselected package python-minimal.
Preparing to unpack .../3-python-minimal_2.7.13-2_amd64.deb ...
Unpacking python-minimal (2.7.13-2) ...
Selecting previously unselected package libpython2.7-stdlib:amd64.
Preparing to unpack .../4-libpython2.7-stdlib_2.7.13-2+deb9u3_amd64.deb ...
Unpacking libpython2.7-stdlib:amd64 (2.7.13-2+deb9u3) ...
Selecting previously unselected package python2.7.
Preparing to unpack .../5-python2.7_2.7.13-2+deb9u3_amd64.deb ...
Unpacking python2.7 (2.7.13-2+deb9u3) ...
Selecting previously unselected package libpython-stdlib:amd64.
Preparing to unpack .../6-libpython-stdlib_2.7.13-2_amd64.deb ...
Unpacking libpython-stdlib:amd64 (2.7.13-2) ...
Setting up libpython2.7-minimal:amd64 (2.7.13-2+deb9u3) ...
Setting up python2.7-minimal (2.7.13-2+deb9u3) ...
Linking and byte-compiling packages for runtime python2.7...
Setting up python-minimal (2.7.13-2) ...
Selecting previously unselected package python.
(Reading database ... 14956 files and directories currently installed.)
Preparing to unpack .../00-python_2.7.13-2_amd64.deb ...
Unpacking python (2.7.13-2) ...
Selecting previously unselected package exim4-config.
Preparing to unpack .../01-exim4-config_4.89-2+deb9u5_all.deb ...
Unpacking exim4-config (4.89-2+deb9u5) ...
Selecting previously unselected package exim4-base.
Preparing to unpack .../02-exim4-base_4.89-2+deb9u5_amd64.deb ...
Unpacking exim4-base (4.89-2+deb9u5) ...
Selecting previously unselected package exim4-daemon-light.
Preparing to unpack .../03-exim4-daemon-light_4.89-2+deb9u5_amd64.deb ...
Unpacking exim4-daemon-light (4.89-2+deb9u5) ...
Selecting previously unselected package exim4.
Preparing to unpack .../04-exim4_4.89-2+deb9u5_all.deb ...
Unpacking exim4 (4.89-2+deb9u5) ...
Selecting previously unselected package libgc1c2:amd64.
Preparing to unpack .../05-libgc1c2_1%3a7.4.2-8_amd64.deb ...
Unpacking libgc1c2:amd64 (1:7.4.2-8) ...
Selecting previously unselected package libwrap0:amd64.
Preparing to unpack .../06-libwrap0_7.6.q-26_amd64.deb ...
Unpacking libwrap0:amd64 (7.6.q-26) ...
Selecting previously unselected package guile-2.0-libs:amd64.
Preparing to unpack .../07-guile-2.0-libs_2.0.13+1-4_amd64.deb ...
Unpacking guile-2.0-libs:amd64 (2.0.13+1-4) ...
Selecting previously unselected package libfribidi0:amd64.
Preparing to unpack .../08-libfribidi0_0.19.7-1+b1_amd64.deb ...
Unpacking libfribidi0:amd64 (0.19.7-1+b1) ...
Selecting previously unselected package libntlm0:amd64.
Preparing to unpack .../09-libntlm0_1.4-8_amd64.deb ...
Unpacking libntlm0:amd64 (1.4-8) ...
Selecting previously unselected package libgsasl7.
Preparing to unpack .../10-libgsasl7_1.8.0-8+b2_amd64.deb ...
Unpacking libgsasl7 (1.8.0-8+b2) ...
Selecting previously unselected package liblzo2-2:amd64.
Preparing to unpack .../11-liblzo2-2_2.08-1.2+b2_amd64.deb ...
Unpacking liblzo2-2:amd64 (2.08-1.2+b2) ...
Selecting previously unselected package libkyotocabinet16v5:amd64.
Preparing to unpack .../12-libkyotocabinet16v5_1.2.76-4.2+b1_amd64.deb ...
Unpacking libkyotocabinet16v5:amd64 (1.2.76-4.2+b1) ...
Selecting previously unselected package mailutils-common.
Preparing to unpack .../13-mailutils-common_1%3a3.1.1-1_all.deb ...
Unpacking mailutils-common (1:3.1.1-1) ...
Selecting previously unselected package mysql-common.
Preparing to unpack .../14-mysql-common_5.8+1.0.2_all.deb ...
Unpacking mysql-common (5.8+1.0.2) ...
Selecting previously unselected package libmariadbclient18:amd64.
Preparing to unpack .../15-libmariadbclient18_10.1.38-0+deb9u1_amd64.deb ...
Unpacking libmariadbclient18:amd64 (10.1.38-0+deb9u1) ...
Selecting previously unselected package libpython2.7:amd64.
Preparing to unpack .../16-libpython2.7_2.7.13-2+deb9u3_amd64.deb ...
Unpacking libpython2.7:amd64 (2.7.13-2+deb9u3) ...
Selecting previously unselected package libmailutils5:amd64.
Preparing to unpack .../17-libmailutils5_1%3a3.1.1-1_amd64.deb ...
Unpacking libmailutils5:amd64 (1:3.1.1-1) ...
Selecting previously unselected package mailutils.
Preparing to unpack .../18-mailutils_1%3a3.1.1-1_amd64.deb ...
Unpacking mailutils (1:3.1.1-1) ...
Selecting previously unselected package netcat-openbsd.
Preparing to unpack .../19-netcat-openbsd_1.130-3_amd64.deb ...
Unpacking netcat-openbsd (1.130-3) ...
Selecting previously unselected package python-pkg-resources.
Preparing to unpack .../20-python-pkg-resources_33.1.1-1_all.deb ...
Unpacking python-pkg-resources (33.1.1-1) ...
Preparing to unpack .../21-rsync_3.1.2-1+deb9u2_amd64.deb ...
Unpacking rsync (3.1.2-1+deb9u2) over (3.1.2-1+deb9u1) ...
Selecting previously unselected package tcpd.
Preparing to unpack .../22-tcpd_7.6.q-26_amd64.deb ...
Unpacking tcpd (7.6.q-26) ...
Preparing to unpack .../23-unzip_6.0-21+deb9u1_amd64.deb ...
Unpacking unzip (6.0-21+deb9u1) over (6.0-21) ...
Selecting previously unselected package python-meld3.
Preparing to unpack .../24-python-meld3_1.0.2-2_all.deb ...
Unpacking python-meld3 (1.0.2-2) ...
Selecting previously unselected package supervisor.
Preparing to unpack .../25-supervisor_3.3.1-1+deb9u1_all.deb ...
Unpacking supervisor (3.3.1-1+deb9u1) ...
Setting up exim4-config (4.89-2+deb9u5) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Adding system-user for exim (v4)
Processing triggers for mime-support (3.60) ...
Setting up mysql-common (5.8+1.0.2) ...
update-alternatives: using /etc/mysql/my.cnf.fallback to provide /etc/mysql/my.cnf (my.cnf) in auto mode
Setting up unzip (6.0-21+deb9u1) ...
Setting up libgc1c2:amd64 (1:7.4.2-8) ...
Setting up libmariadbclient18:amd64 (10.1.38-0+deb9u1) ...
Setting up netcat-openbsd (1.130-3) ...
update-alternatives: using /bin/nc.openbsd to provide /bin/nc (nc) in auto mode
Setting up rsync (3.1.2-1+deb9u2) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of restart.
Setting up libntlm0:amd64 (1.4-8) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Setting up guile-2.0-libs:amd64 (2.0.13+1-4) ...
Setting up libfribidi0:amd64 (0.19.7-1+b1) ...
Setting up cron (3.0pl1-128+deb9u1) ...
Adding group `crontab' (GID 102) ...
Done.
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up libpython2.7-stdlib:amd64 (2.7.13-2+deb9u3) ...
Setting up liblzo2-2:amd64 (2.08-1.2+b2) ...
Setting up libwrap0:amd64 (7.6.q-26) ...
Setting up mailutils-common (1:3.1.1-1) ...
Setting up libgsasl7 (1.8.0-8+b2) ...
Setting up python2.7 (2.7.13-2+deb9u3) ...
Setting up exim4-base (4.89-2+deb9u5) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
exim: DB upgrade, deleting hints-db
Setting up tcpd (7.6.q-26) ...
Setting up libpython-stdlib:amd64 (2.7.13-2) ...
Setting up libpython2.7:amd64 (2.7.13-2+deb9u3) ...
Setting up exim4-daemon-light (4.89-2+deb9u5) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Initializing GnuTLS DH parameter file
Setting up libkyotocabinet16v5:amd64 (1.2.76-4.2+b1) ...
Setting up python (2.7.13-2) ...
Setting up libmailutils5:amd64 (1:3.1.1-1) ...
Setting up python-meld3 (1.0.2-2) ...
Setting up python-pkg-resources (33.1.1-1) ...
Setting up mailutils (1:3.1.1-1) ...
update-alternatives: using /usr/bin/frm.mailutils to provide /usr/bin/frm (frm) in auto mode
update-alternatives: using /usr/bin/from.mailutils to provide /usr/bin/from (from) in auto mode
update-alternatives: using /usr/bin/messages.mailutils to provide /usr/bin/messages (messages) in auto mode
update-alternatives: using /usr/bin/movemail.mailutils to provide /usr/bin/movemail (movemail) in auto mode
update-alternatives: using /usr/bin/readmsg.mailutils to provide /usr/bin/readmsg (readmsg) in auto mode
update-alternatives: using /usr/bin/dotlock.mailutils to provide /usr/bin/dotlock (dotlock) in auto mode
update-alternatives: using /usr/bin/mail.mailutils to provide /usr/bin/mailx (mailx) in auto mode
Setting up supervisor (3.3.1-1+deb9u1) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up exim4 (4.89-2+deb9u5) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Removing intermediate container 2054bf3f732c
 ---> 4f758752145c
Step 4/8 : COPY run.sh /run.sh
 ---> 2ed08af60da7
Step 5/8 : COPY build_env.sh /build_env.sh
 ---> aa982f9fb69c
Step 6/8 : COPY dist/ /dist
 ---> dd950d55508f
Step 7/8 : ENV SERVER_FLAVOR=nginx     PHP_FPM_CONFIG=/etc/php/7.0/fpm     PHP_FPM_PATH=/usr/sbin/php-fpm7.0
 ---> Running in 5b63c922dbf5
Removing intermediate container 5b63c922dbf5
 ---> 5163630ed320
Step 8/8 : ENTRYPOINT [ "/bin/bash", "/run.sh" ]
 ---> Running in ebd7b6f1f689
Removing intermediate container ebd7b6f1f689
 ---> 395d880849f9
Successfully built 395d880849f9
Successfully tagged platform-release_ushahidi:latest
Creating platform-release_mysql_1 ... done
Creating platform-release_ushahidi_1 ... done
Attaching to platform-release_mysql_1, platform-release_ushahidi_1
mysql_1     | [i] MySQL data directory not found, creating initial DBs
mysql_1     | 2019-08-09 14:52:43 140028034231112 [Note] /usr/bin/mysqld (mysqld 10.1.32-MariaDB) starting as process 33 ...
mysql_1     | 2019-08-09 14:52:44 7f5ad13d2b48 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
mysql_1     | 
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Using mutexes to ref count buffer pool pages
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: The InnoDB memory heap is disabled
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Using Linux native AIO
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Using SSE crc32 instructions
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Initializing buffer pool, size = 16.0M
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Completed initialization of buffer pool
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: The first specified data file /var/lib/mysql/ibdata1 did not exist: a new database to be created!
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Setting file /var/lib/mysql/ibdata1 size to 10 MB
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Setting log file /var/lib/mysql/ib_logfile101 size to 5 MB
mysql_1     | 2019-08-09 14:52:44 140028034231112 [Note] InnoDB: Setting log file /var/lib/mysql/ib_logfile1 size to 5 MB
mysql_1     | 2019-08-09 14:52:45 140028034231112 [Note] InnoDB: Renaming log file /var/lib/mysql/ib_logfile101 to /var/lib/mysql/ib_logfile0
mysql_1     | 2019-08-09 14:52:45 140028034231112 [Warning] InnoDB: New log files created, LSN=45781
mysql_1     | 2019-08-09 14:52:45 140028034231112 [Note] InnoDB: Doublewrite buffer not found: creating new
mysql_1     | 2019-08-09 14:52:46 140028034231112 [Note] InnoDB: Doublewrite buffer created
mysql_1     | 2019-08-09 14:52:46 140028034231112 [Note] InnoDB: 128 rollback segment(s) are active.
mysql_1     | 2019-08-09 14:52:46 140028034231112 [Warning] InnoDB: Creating foreign key constraint system tables.
mysql_1     | 2019-08-09 14:52:46 140028034231112 [Note] InnoDB: Foreign key constraint system tables created
mysql_1     | 2019-08-09 14:52:46 140028034231112 [Note] InnoDB: Creating tablespace and datafile system tables.
mysql_1     | 2019-08-09 14:52:47 140028034231112 [Note] InnoDB: Tablespace and datafile system tables created.
mysql_1     | 2019-08-09 14:52:47 140028034231112 [Note] InnoDB: Waiting for purge to start
mysql_1     | 2019-08-09 14:52:47 140028034231112 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.38-83.0 started; log sequence number 0
mysql_1     | 2019-08-09 14:52:47 140027809258160 [Note] InnoDB: Dumping buffer pool(s) not yet started
mysql_1     | 2019-08-09 14:52:47 140027809069744 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
ushahidi_1  | + export PLATFORM_HOME=/var/www/html
ushahidi_1  | + PLATFORM_HOME=/var/www/html
ushahidi_1  | + export PLATFORM_API_HOME=/var/www/html/platform
ushahidi_1  | + PLATFORM_API_HOME=/var/www/html/platform
ushahidi_1  | ++ dirname /run.sh
ushahidi_1  | + . //build_env.sh
ushahidi_1  | ++ client_version=v4.0.0
ushahidi_1  | ++ api_version=v4.0.0
ushahidi_1  | ++ release_version=v4.0.0
ushahidi_1  | ++ client_url=
ushahidi_1  | ++ api_url=
ushahidi_1  | ++ client_tar=ushahidi-platform-client-bundle-v4.0.0.tar.gz
ushahidi_1  | ++ api_tar=ushahidi-platform-bundle-v4.0.0.tar.gz
ushahidi_1  | + [[ -z ushahidi-platform-client-bundle-v4.0.0.tar.gz ]]
ushahidi_1  | + [[ -z ushahidi-platform-bundle-v4.0.0.tar.gz ]]
ushahidi_1  | + '[' -z '' ']'
ushahidi_1  | + client_url=https://github.com/ushahidi/platform-client/releases/download/v4.0.0/ushahidi-platform-client-bundle-v4.0.0.tar.gz
ushahidi_1  | + '[' -z '' ']'
ushahidi_1  | + api_url=https://github.com/ushahidi/platform/releases/download/v4.0.0/ushahidi-platform-bundle-v4.0.0.tar.gz
ushahidi_1  | + release_target_folder=/tmp/release/ushahidi-platform-release-v4.0.0
ushahidi_1  | + case "$1" in
ushahidi_1  | + fetch
ushahidi_1  | + '[' '!' -d /tars ']'
ushahidi_1  | + '[' '!' -f /tars/ushahidi-platform-client-bundle-v4.0.0.tar.gz ']'
ushahidi_1  | + '[' '!' -f /tars/ushahidi-platform-bundle-v4.0.0.tar.gz ']'
ushahidi_1  | + build
ushahidi_1  | + mkdir -p /tmp/client
ushahidi_1  | + tar -C /tmp/client -xz -f /tars/ushahidi-platform-client-bundle-v4.0.0.tar.gz
ushahidi_1  | + mkdir -p /tmp/api
ushahidi_1  | + tar -C /tmp/api -xz -f /tars/ushahidi-platform-bundle-v4.0.0.tar.gz
ushahidi_1  | 
ushahidi_1  | gzip: stdin: unexpected end of file
ushahidi_1  | tar: Unexpected EOF in archive
ushahidi_1  | tar: Unexpected EOF in archive
ushahidi_1  | tar: Error is not recoverable: exiting now
^CGracefully stopping... (press Ctrl+C again to force)
Stopping platform-release_ushahidi_1 ... done
Stopping platform-release_mysql_1    ... done

Github release script better handle descriptions

Any descriptions entered through github are overwritten and set to blank when re-releasing the same tag. We could

  1. write the description in a file in the repo, so that the script sends it to github in our behalf or
  2. do some more scripting so that if there is a description is set, we send it again when editing the release.

@rjmackay what do you think would work best?

Deployments don't work with the mobile app

Deployments created with this repo do not work out of the box with the mobile app. The problem has been isolated to the file config.json having a relative URL instead of an absolute one.

Out of the box, the config.json file look something like this:

{
	"client_id": "ushahidiui",
	"client_secret": "35e7f0bca957836d05ca0492211b0ac707671261",
        "backend_url": "/",
	"google_analytics_id": "",
	"intercom_app_id": "",
	"mapbox_api_key": "... key here ...",
	"raven_url": ""
}

in order for the mobile app to be able to add the deployment, you would need to change the value for "backend_url" to the full URL of your site. I.e. if your site is hosted at https://my.ushahidi.example.com , the line should read:

     "backend_url": "https://my.ushahidi.example.com",

This will need to be added to the documentation and there could be some instrumentation in the docker-based start up sequence , to better inform about this and to make the necessary adjustments based on the value of an environment variable (i.e. PLATFORM_URL).

Bug After Installing Ushahidi Platform

After installing Ushahidi admin account can not change the settings
The resolution that Khalid Elshafie found is to login to the MySQL database and update the admin roles
using the following SQL statement

Each() function deprecated

When performing the database migration I get:

"status": "Deprecated",
"title": "The each() function is deprecated. This message will be suppressed on further calls",
"message": "The each() function is deprecated. This message will be suppressed on further calls",
"class": "ErrorException",
"file": "/var/www/html/platform/vendor/aura/di/src/Factory.php",
"line": 622,

Unnecessary Warnings in Logs from Sentry-Laravel

My logs are a bit chatty due to a warning from the worker pool that I believe is getting triggered by Sentry. With every request, the following is getting logged:

"fatal: not a git repository: '/var/www/html/platform/.git"

I'm not using Sentry, and I don't really plan on using it at the moment. Is there a way to adjust my config, so Sentry is no longer throwing error messages?

MYSQL Problem installing ushahidi running docker compose

This is for the ushihidi version 4

These are the logs when i used docker-compose up

platform_tasks_1  | COMMAND OPTIONS {'--config': '/etc/chaperone.d',
platform_tasks_1  |  '--create-user': None,
platform_tasks_1  |  '--debug': True,
platform_tasks_1  |  '--default-home': None,
platform_tasks_1  |  '--disable-services': False,
platform_tasks_1  |  '--exitkills': False,
platform_tasks_1  |  '--force': False,
platform_tasks_1  |  '--ignore-failures': False,
platform_tasks_1  |  '--log-level': 'DEBUG',
platform_tasks_1  |  '--no-console-log': False,
platform_tasks_1  |  '--no-defaults': False,
platform_tasks_1  |  '--no-exitkills': False,
platform_tasks_1  |  '--no-syslog': False,
platform_tasks_1  |  '--show-dependencies': False,
platform_tasks_1  |  '--task': False,
platform_tasks_1  |  '--user': None,
platform_tasks_1  |  '--version': False,
platform_tasks_1  |  '<args>': [],
platform_tasks_1  |  '<command>': None}
platform_tasks_1  | Jan 18 16:24:05 55ca6c3b10b1 chaperone[1]: Switching all chaperone logging to /dev/log
platform_tasks_1  | Jan 18 16:24:05 55ca6c3b10b1 chaperone[1]: chaperone version 0.3.9, ready.
platform_1        | Phinx by Rob Morgan - https://phinx.org. 0.8.1
platform_1        |
platform_1        | using config file ./phinx.php
platform_1        | using config parser php
platform_1        | using migration paths
platform_1        |  - /var/www/migrations
platform_1        | using seed paths
platform_1        |  - /var/www/seeds
platform_1        | warning no environment specified, defaulting to: ushahidi
platform_1        | using adapter mysql
platform_1        | using database
platform_1        |
platform_1        | In MysqlAdapter.php line 115:
platform_1        |
platform_1        |   There was a problem connecting to the database: SQLSTATE[HY000] [1045] Acce
platform_1        |   ss denied for user ''@'172.18.0.2' (using password: NO)

Following the guides provided in the link
https://www.ushahidi.com/support/install-ushahidi
https://github.com/ushahidi/platform-release/releases
also lead to the same issue

some links are broken i think even with some onewith mysql knowledge as the guide mentioned this needs to be rewritten

The "Combine nearby posts" option displays clusters where there are None

Hi there,
I am running my own deployment of Ushahidi, using the latest version:

https://github.com/ushahidi/platform-release/releases/tag/v6.0.0

When I tick the checkbox "Combine nearby posts" I see that the posts are clustered on the map.
However I also see that sometimes when there is only one post in a location, Ushahidi displays it as a cluster of 2.

cluster_of_2_is_really_one_post cluster_of_2_is_really_one_post_expanded

In the above screenshot you can see a cluster of 2, which I can expand to show two post icons. However these are the same post.
I have exported the data and double-checked to make sure that there is no duplicate data.

I am not sure if the following settings a relevant, but I am supplying them to you just in case:
Default base layer: Streets
Default zoom level: 16
Map Precision Level: 2

Can run in subdirectory as loading of config.js and .css files fails

Probably a rather easy fix, but I can't get my Nginx to properly load the config.js and the .css files requested by the index.html.

The setup I am trying to get working is that the html directory is not in the root of the webserver, but rather is the /ushahidi subfolder, so that https://mydomain.com/ushahidi loads the index.html file.

This works fine so far, however I only get the "Sorry, something went wrong. Try reloading the page." message as the browser tries to load the config.js etc. files from https://mydomain.com/confg.js instead of https://mydomain.com/ushahidi/config.js as it should.

Thanks for the help ๐Ÿ˜„

Can't connect database if it isn't in localhost

I'm trying to install U 3.x using your tutorial. In my case, the database is in a separate host.
When I try to make migrations I got a "can't" connect error.

I fixed editing by hand your parameters in phinx.php and putting my own values, ie:
host: myhost (instead of variable you put there)
database: mydb (idem)

I double checked .env file and values are correct.

Uploaded Images not showing up in 3.7

I've found this bug, but still can't find a solution, I've found other users with the same problems
foruns
And basically, the images are inside the right upload folder, in /var/www/html/platform/application/media/uploads/ with chmod 777 all over, but when we try to access it trough URL it returns a blank screen.

This is happening in Image fields and logo, it seems that ushahidi can't find image files.

I'm running with NGINX confs:

server {
        listen *:80 default_server;

        #
        root /var/www/html;

        # Force encoding.
        charset utf-8;
        override_charset on;

        location /platform {
                fastcgi_param   QUERY_STRING            $query_string;
                fastcgi_param   REQUEST_METHOD          $request_method;
                fastcgi_param   CONTENT_TYPE            $content_type;
                fastcgi_param   CONTENT_LENGTH          $content_length;

                fastcgi_split_path_info         ^(/platform/)(.*)$;

                fastcgi_param   SCRIPT_FILENAME         $document_root/platform/httpdocs/index.php;
                fastcgi_param   SCRIPT_NAME             $fastcgi_script_name;
                fastcgi_param   PATH_INFO               $fastcgi_path_info;
                fastcgi_param   PATH_TRANSLATED         $document_root$fastcgi_path_info;
                fastcgi_param   REQUEST_URI             $request_uri;
               fastcgi_param   DOCUMENT_URI            $document_uri;
                fastcgi_param   DOCUMENT_ROOT           $document_root;
                fastcgi_param   SERVER_PROTOCOL         $server_protocol;

                fastcgi_param   GATEWAY_INTERFACE       CGI/1.1;
                fastcgi_param   SERVER_SOFTWARE         nginx/$nginx_version;

                fastcgi_param   REMOTE_ADDR             $remote_addr;
                fastcgi_param   REMOTE_PORT             $remote_port;
                fastcgi_param   SERVER_ADDR             $server_addr;
                fastcgi_param   SERVER_PORT             $server_port;
                fastcgi_param   SERVER_NAME             $server_name;

                fastcgi_param   HTTPS                   $https;

                fastcgi_pass    localhost:9000;
                fastcgi_pass_header Authorization;
        }

        location / {
                try_files $uri $uri/ /index.html;
        }
}

Just like this repository file, but I've changed the location:

        location / {
                try_files $uri $uri/ /index.html;
        }

In a hope to fix the problem, according to NGINX documentation for Angular (https://github.com/angular-ui/ui-router/wiki/Frequently-Asked-Questions#how-to-configure-your-server-to-work-with-html5mode) given by @tuxpiper in the community foruns...

thks for any help, I'm really needing it....

problem deleting field on survey

On a new survey , once a field is created it cannot be deleted.
The message that appears on JS console is ..

vendor.7772a1d529dcfbc6af6d.js:102 DELETE http://carreteras.intelect.com.mx/api/v3/forms/10/attributes/39?order=asc&orderby=priority 500 (Internal Server Error)

and

vendor.7772a1d529dcfbc6af6d.js:102 Possibly unhandled rejection: {"data":{"errors":[{"status":500,"message":"This cache store does not support tagging."}]}," ...

this message "This cache store does not support tagging." appeared also with no consequence whe creating new surveys. (ataching image)
Surveys - Carreteras

using docker version https://github.com/ushahidi/platform-release.git, as of Dec 5 2019

My .env ..

APP_ENV=local
APP_DEBUG=false
APP_KEY=h1N8OnHDGNzCbA$wfoveR(rXGHn0sq%o
APP_TIMEZONE=UTC

DB_CONNECTION=mysql
DB_HOST=mysql
DB_DATABASE=ushahidi
DB_USERNAME= ****
DB_PASSWORD= ****
DB_TYPE=MySQLi

CACHE_DRIVER=file
QUEUE_DRIVER=sync

how to login with default admin?

Sorry for the stupid question, I'm a total newbie with ushahidi.

After docker-compose starting, the server runs correctly but I am not able to login with an admin account.

The login form ask me a valid email address.. admin is not a valid email address (missing @)

I can register new users, but with a new user I don't see the "settings" button (I guess for missing permissions)

Thanks

ERROR: for platform-release_ushahidi_1 a bytes-like object is required, not 'str'

When I run command docker-compose up so error occured please check..

ERROR: for platform-release_ushahidi_1 a bytes-like object is required, not 'str'

ERROR: for ushahidi a bytes-like object is required, not 'str'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/docker/api/client.py", line 261, in _raise_for_status
response.raise_for_status()
File "/usr/lib/python3/dist-packages/requests/models.py", line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.22/containers/832ab0b5d7e25aff1d3be7b929d44ba47023dc0dc67d1258439f5f0d1aa7729d/start

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/compose/service.py", line 625, in start_container
container.start()
File "/usr/lib/python3/dist-packages/compose/container.py", line 241, in start
return self.client.start(self.id, **options)
File "/usr/lib/python3/dist-packages/docker/utils/decorators.py", line 19, in wrapped
return f(self, resource_id, *args, **kwargs)
File "/usr/lib/python3/dist-packages/docker/api/container.py", line 1095, in start
self._raise_for_status(res)
File "/usr/lib/python3/dist-packages/docker/api/client.py", line 263, in _raise_for_status
raise create_api_error_from_http_exception(e)
File "/usr/lib/python3/dist-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
raise cls(e, response=response, explanation=explanation)
docker.errors.APIError: 500 Server Error: Internal Server Error ("b'driver failed programming external connectivity on endpoint platform-release_ushahidi_1 (07929a84c1540792b8bc86aa2f2f95636e78ed83c82c64bf2e2ae6d16de26d17): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use'")

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/bin/docker-compose", line 11, in
load_entry_point('docker-compose==1.25.0', 'console_scripts', 'docker-compose')()
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 72, in main
command()
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 128, in perform_command
handler(command, command_options)
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 1107, in up
to_attach = up(False)
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 1088, in up
return self.project.up(
File "/usr/lib/python3/dist-packages/compose/project.py", line 565, in up
results, errors = parallel.parallel_execute(
File "/usr/lib/python3/dist-packages/compose/parallel.py", line 112, in parallel_execute
raise error_to_reraise
File "/usr/lib/python3/dist-packages/compose/parallel.py", line 210, in producer
result = func(obj)
File "/usr/lib/python3/dist-packages/compose/project.py", line 548, in do
return service.execute_convergence_plan(
File "/usr/lib/python3/dist-packages/compose/service.py", line 567, in execute_convergence_plan
return self._execute_convergence_start(
File "/usr/lib/python3/dist-packages/compose/service.py", line 506, in _execute_convergence_start
_, errors = parallel_execute(
File "/usr/lib/python3/dist-packages/compose/parallel.py", line 112, in parallel_execute
raise error_to_reraise
File "/usr/lib/python3/dist-packages/compose/parallel.py", line 210, in producer
result = func(obj)
File "/usr/lib/python3/dist-packages/compose/service.py", line 508, in
lambda c: self.start_container_if_stopped(c, attach_logs=not detached, quiet=True),
File "/usr/lib/python3/dist-packages/compose/service.py", line 620, in start_container_if_stopped
return self.start_container(container)
File "/usr/lib/python3/dist-packages/compose/service.py", line 627, in start_container
if "driver failed programming external connectivity" in ex.explanation:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.