aboutsummaryrefslogtreecommitdiffstats
path: root/docker-compose.yml (follow)
Commit message (Collapse)AuthorAgeLines
* Bump psql version in docker-composeGravatar Boris Muratov2022-10-28-1/+1
|
* Remove IP From Compose PortsGravatar Hassan Abouelela2022-07-12-3/+3
| | | | | | | | Specifying the port IP in compose seems to significantly slow down networking with postgres. This effect is epically noticeable in tests, which are 5-10x faster with the change. Signed-off-by: Hassan Abouelela <[email protected]>
* Move psql health check to docker compose fileGravatar Chris Lovering2021-09-17-1/+7
|
* Init metricity using docker-compose init volumeGravatar Chris Lovering2021-09-17-0/+2
|
* Initialise metricity at runtimeGravatar Chris Lovering2021-09-06-2/+0
| | | | | | Currently the bot cannot start in dev as the site errors, saying that metricity doesn't exist. Previously this note existing was fine, unless you needed to use metricity data. With the recent addition of django-prometheus, metricity is now required on boot. This PR moves the init of metricity from a docker-compose volume, into running of the site. This means that external projects using site, that don't have access to the init.sql file to mount a volume, now also init metricity.
* Docker-compose: upgrade to postgres 13Gravatar Matteo Bertucci2021-06-27-1/+1
| | | We have been using postgres 13 in production for a long time, but we never actually updated the docker-compose environment.
* Upgrade site to Python 3.9.Gravatar Leon Sandøy2020-11-14-1/+2
|
* Added metricity db connection and user bot APIGravatar Lucas Lindström2020-10-06-0/+3
|
* Fix #329 missing manage.py & Django logsGravatar MarkKoz2020-02-16-0/+1
| | | | Fixed by allocating a pseudo-tty to the web service in Docker Compose.
* Bump PostgreSQL in compose.Gravatar Johannes Christ2019-10-11-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This might break local PostgreSQL containers with the following error: postgres_1 | 2019-10-11 20:01:48.772 UTC [1] FATAL: database files are incompatible with server postgres_1 | 2019-10-11 20:01:48.772 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.0. You will need to do one of the following: - Delete the old data volume and start from scratch (simple, recommended). As we don't have an explicit volume configured, only the one the PostgreSQL image uses, this is as simple as running `docker-compose stop` followed by `docker-compose rm`. Afterwards, you can restart it. - The dump & restore route. Do this if you don't want to delete your container data. To do this, first switch the PostgreSQL version in `docker-compose.yml` back to `11`, then run the following commands: docker-compose stop # Stop all containers docker-compose start postgres # Start the database docker-compose exec postgres pg_dumpall -U pysite > db.sql # Pull a SQL dump docker-compose stop # Stop the containers again docker-compose rm # Remove the containers Now, update the PostgreSQL version in `docker-compose.yml` to `12` again, and run the following commands: docker-compose up -d postgres # Start the database docker-compose exec -T postgres psql -U pysite < db.sql # Pull in the dump rm db.sql # Cleanup garbage, if you want If you're on Windows, then I can't help you. Sorry.
* Support internal docker network DNS resolution & dev ALLOWED_HOSTS env var.Gravatar scragly2019-09-28-0/+6
|
* Create custom manage.py entry point, remove scripts and merge Dockerfile.Gravatar scragly2019-09-28-3/+2
|
* Change CI DB setup to use docker.Gravatar scragly2019-09-21-2/+2
|
* Refine DockerfilesGravatar scragly2019-09-18-1/+1
|
* Setting up a method for automatically applying migrations in production. ↵Gravatar Leon Sandøy2019-07-03-4/+2
| | | | Making a separate Dockerfile for local docker-compose builds.
* makemigrations pipeline created, RepoData model created, and a really naive ↵Gravatar Leon Sandøy2019-04-16-1/+3
| | | | implementation of the API stuff which makes 6 requests and takes forever to load. I've found a better approach so I'm gonna switch to that next.
* Use volume for staticfiles.Gravatar Johannes Christ2019-04-07-1/+5
|
* Remove bot from compose setup, move staticfiles to writable directory.Gravatar Johannes Christ2019-04-07-7/+1
|
* Address review by @jchristgitGravatar Gareth Coles2019-04-05-4/+4
|
* pysite -> pydis_siteGravatar Gareth Coles2019-04-05-3/+3
|
* Add an example `docker-compose.yml`.Gravatar Johannes Christ2019-01-13-7/+16
|
* Only listen on localhost.Gravatar Johannes Christ2018-10-15-1/+4
|
* Update the compose file and dockerapp file.Gravatar Johannes Christ2018-10-06-0/+31
| | | | The development app from the compose file will now apply migrations on boot and additionally, it will use Django's development server along with the current directory mounted read-only into the container in order to support code reloading, helpful while development.
* Remove `docker-compose.yml`.Gravatar Johannes Christ2018-09-20-34/+0
|
* Add a `docker-compose.yml` file.Gravatar Johannes Christ2018-09-05-0/+34
|
* Remove unused files.Gravatar Johannes Christ2018-08-22-28/+0
|
* updates docker-compose, changes default rdb port and handles a socket error ↵Gravatar Christopher Baklid2018-07-08-37/+17
| | | | in service discovery
* updates docker-compose file [ci skip]Gravatar Christopher Baklid2018-05-20-8/+5
|
* Docker compose (#40)Gravatar Christopher Baklid2018-03-25-0/+51
* adds docker-compose file * cleanup * adds template auto reload to vagrant box * Update index.html
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-17 22:29:11 +0000