Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

atualizando nome do arquivo dump do banco de dados #91

Closed
wants to merge 2 commits into from
Closed

atualizando nome do arquivo dump do banco de dados #91

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
887a076
atualizando nome do arquivo dump do banco de dados
felipemelzfwm May 13, 2024
64bc786
adicionando caminho relativo
felipemelzfwm May 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Se estiver usando Docker, os comandos para carregar o dump são:

```bash
# Copiar o dump para a pasta temporária do Docker
docker exec -it cp backup.sql POSTGRES_CONTAINER_ID:/tmp/backup.sql
docker exec -it cp prisma/dev_dump.sql POSTGRES_CONTAINER_ID:/tmp/backup.sql
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testando esse comando não rodou como esperado na minha máquina.

docker exec -it cp backup.sql POSTGRES_CONTAINER_ID:/tmp/backup.sql
Error response from daemon: No such container: cp

What's next?
  Try Docker Debug for seamless, persistent debugging tools in any container or image → docker debug cp
  Learn more at https://docs.docker.com/go/debug-cli/

O comando que funcionou aqui foi:

docker cp prisma/dev_dump.sql POSTGRES_CONTAINER_ID:/tmp/backup.sql

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pensando em uma sequência lógica de passos para a configuração do ambiente, o ideal é mover essa sessão referente aos seeds do banco para depois da configuração do servidor. Logo após rodar as migrations.

Sugiro essa alteração, pq não faz sentido hidratar o banco antes de criar o banco, e ter as tabelas, processo esse feito pelas migrations. E incluindo essa informação antes do setup do projeto, pode levar um entendimento incorreto do fluxo. Sendo assim, acredito que a sequência ideal seria:

  1. Clone o repositório:
  2. Instale as dependências:
  3. Aplique o dump do banco
  4. Inicie o servidor:

# Importar o dump para o banco
docker exec -i POSTGRES_CONTAINER_ID psql -U root -d DATABASE_NAME -f /tmp/backup.sql
```
Expand Down