| Commit message (Collapse) | Author | Age | Lines |
|
|
| |
We have been using postgres 13 in production for a long time, but we never actually updated the docker-compose environment.
|
| |
|
| |
|
|
|
|
| |
Fixed by allocating a pseudo-tty to the web service in Docker Compose.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Making a separate Dockerfile for local docker-compose builds.
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
in service discovery
|
| |
|
|
* adds docker-compose file
* cleanup
* adds template auto reload to vagrant box
* Update index.html
|