- 22 May, 2019 6 commits
-
-
Philippe Pepiot authored
Otherwise, mails sent by cubicweb-blog have a subject prefix "[instance]". We want "[intranet]" here. Use CW_INSTANCE_NAME build arg from docker-cubicweb for this.
-
Philippe Pepiot authored
Following f1bb764393a2, the instance name is not "instance".
-
Philippe Pepiot authored
instance is now named "instance"
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
The image contains all we need except we use a modified pyramid.ini
-
- 16 May, 2019 1 commit
-
-
Philippe Pepiot authored
-
- 07 May, 2019 15 commits
-
-
Philippe Pepiot authored
So if the new container don't start correctly within 3 minutes, the command will exit with status 1 and fail the build.
-
Philippe Pepiot authored
-
Philippe Pepiot authored
This is actually the way we run our instance. Add a "make deploy" target which applies the deployment with newer image and trigger a rolling-release.
-
Philippe Pepiot authored
Otherwise our registry (harbor) fail to regonize the digests are already present... This is weird.
-
Philippe Pepiot authored
-
Philippe Pepiot authored
Prune debian directory but keep docker related files since its referenced from README.rst which is shipped in sdist
-
Philippe Pepiot authored
-
Philippe Pepiot authored
Since it's rst file
-
Philippe Pepiot authored
The files are never present in /etc/cubicweb.d/intranet/i18n because "db-create" does not run here. This ensure i18n catalogs are up-to-date.
-
Philippe Pepiot authored
/etc/cubicweb.d/intranet/data is never present at docker startup, so the test is useless.
-
Philippe Pepiot authored
Since we now install /src in editable mode, just mounting the source in /src is enough to have a working "dev" environment. Move "hints" command to the README.
-
Philippe Pepiot authored
Also install setuptools from debian package since the setuptools version is now high enough to install Markdown, see previous changeset "Drop use of pipenv".
-
Philippe Pepiot authored
flake8 doesn't require the source to be installed
-
Philippe Pepiot authored
This is no longer useful with related cubes being released for py3 & new style cube.
-
Philippe Pepiot authored
See https://lists.cubicweb.org/pipermail/cubicweb-devel/2019-May/002818.html I think pipenv will add maintance cost we don't need here. Install additional requirements from docker/requirements.txt file. Install cubicweb-intranet in editable mode in /src Install setuptools with pip because the version in stretch doesn't work with the latest Markdown version :/
-
- 24 Apr, 2019 16 commits
-
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
-
Philippe Pepiot authored
This allow to develop cubicweb-intranet with docker. make dev will: * build image * run a container with code mounted in /src * install cubicweb-intranet in editable (develop) mode from /src * spawn an interactive shell in the container It mean we can edit the source code locally and run/test it in the container.
-
Philippe Pepiot authored
This help to run the image using a local postgresql server with peer authentication through unix socket (for testing).
-
Philippe Pepiot authored
The makefile is used to run various commands related to docker (build, push).
-
Philippe Pepiot authored
* install dependencies with pipenv (so we can control upgrades and have a reproductible build). * install current source code for cubicweb-intranet * handle instance creation with pyramid.ini with redis sessions * handle database upgrades
-
Philippe Pepiot authored
We use cubicweb-bootstrap in our instance and this conflict with cubicweb-bootstrap. The file uiprops.py was manually dropped from our production instance. So I think we can drop this.
-
- 23 Apr, 2019 2 commits
-
-
Philippe Pepiot authored
-
Philippe Pepiot authored
I don't know why it was added but we don't have any Repository entity in our instance. So just drop it. Keep the depencency since we can't run "drop_cube()" without having the cube installed...
-