churchcrm / docker Goto Github PK

Use docker image branch crm-docker-rewrite with churchcrm V3.0.9
When change sLangeuage, the web also show en_US

Hey,

I've tried a new install and I'm getting the following error:

PHP Fatal error: Uncaught Error: Call to undefined function mysqli_connect()

Seems the image is missing msqli?

More here: ChurchCRM/CRM#810

Hi, I am having the below error when performing backup.
Error making API Call to: /api/database/backup
Error text: Cannot compress entire archive with gzip, enable ext/zlib in php.ini

May I know how to edit php.ini in ChurchCRM Docker?

After starting the docker image I'm getting this error:

I think this should [also | exclusively] listen on SSH by default with a self signed cert.

It'll throw some warnings at user's browsers, but it should be secure by default

What does docker have in the way of cert utilities?

I get the above error when I install and run the Docker image of ChurchCRM. I'm not sure what to do. Thank you in advance.

We are about to release 3.0.0, and it is unclear how to make a new build with this repo. The current build is 2.7.5 which is over a year old.

Link the database and web app container so that the initial setup is not necessary, since the CRM Administrator is setting the password at the time he/she provisions the database.

See documentation here regarding linking docker containers and sharing environment variables;
http://www.shogan.co.uk/docker/deploying-a-simple-linked-container-web-app-with-docker/

can you update the docker repo so that it only pulls full releases?
no more RCs for docker now that 2.4.0 is GA

Just a talking point, it might be good to break the containers up to single process docker images.

This way the most simple configuration - closest to the "official images" - can be used.

@jaskipper

System:
Windows 10 Home, Docker Tools 64

After changing the default passwords, I tried to build and receive this error

Step 1 : FROM jaskipper/alpine-apache-php7
 ---> 78ccb0ae3896
Step 2 : MAINTAINER ChurchCRM
 ---> Using cache
 ---> 363192a154e7
Step 3 : RUN apk update && apk upgrade &&     printf "Build of skipper/alpine-apache, date: %s\n"  `date -u +"%Y-%m-%dT%H:%M:%SZ"` >> /etc/BUILD
 ---> Running in 162d40fcaabf
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
fetch http://dl-4.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://dl-4.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
fetch https://nl.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
v3.4.6-44-g5076b2f [http://dl-cdn.alpinelinux.org/alpine/v3.4/main]
v3.4.6-33-g38ef2d2 [http://dl-cdn.alpinelinux.org/alpine/v3.4/community]
v3.5.0-446-gfb41b70411 [http://dl-4.alpinelinux.org/alpine/edge/community]
v3.5.0-444-gca2e022e48 [http://dl-4.alpinelinux.org/alpine/edge/testing]
v3.5.0-446-gfb41b70411 [https://nl.alpinelinux.org/alpine/edge/main]
OK: 15830 distinct packages available
ERROR: unsatisfiable constraints:
  icu-libs-58.2-r1:
    masked in: @edge
    satisfies:
               php7-intl-7.0.14-r5[so:libicui18n.so.58]
               php7-intl-7.0.14-r5[so:libicuio.so.58]
               php7-intl-7.0.14-r5[so:libicuuc.so.58]

�[31mERROR�[0m: Service 'churchcrm' failed to build: The command '/bin/sh -c apk update && apk upgrade &&     printf "Build of skipper/alpine-apache, date: %s\n"  `date -u +"%Y-%m-%dT%H:%M:%SZ"` >> /etc/BUILD' returned a non-zero code: 2

Any Ideas as to the issue?

Use docker image branch crm-docker-rewrite
build Dockerfile need add php7-zip

rewrite issue at AppIntegrityService.php
it will send to nginx server, but churchcrm docker image apache don't send the port information.

Hi, I am new here.
May i know how to perform upgrade ChurchCRM in Docker?

Secrets are tricky to do well. But it seems that many think having them in the ENV is a bad idea.

Some opinion around the issue.

I propose that config is stored in the ENV, but Secrets are moved to files that are mounted as volumes with restricted access. This is basically how Dockers own Secrets system works.

Some guidance as to why this is a good idea.

Basically, this would mean that a file represents either one secret, or a bunch of secrets are stored in one file. Mariadb/Mysql already supports reading secrets from a file.

The official MariaDB allows the use of secrets.