aboutsummaryrefslogtreecommitdiffstats
path: root/docker-compose.yml (follow)
Commit message (Collapse)AuthorAgeLines
* 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-18 04:53:31 +0000