Merge pull request #57 from omics-datascience/dev

Dev

DEPLOYING.md

@@ -126,8 +126,8 @@ You can use set Modulector DB in two ways.
 
 1. Start up a PostgreSQL service. You can use the same service listed in the `docker-compose.dev.yml` file. Run `docker compose -f docker-compose.dev.yml up -d db_modulector` to start the DB service.
 1. **Optional but recommended (you can omit these steps if it's the first time you are deploying Modulector)**: due to major changes, it's probably that an import thrown several errors when importing. To prevent that you could do the following steps before doing the importation:
-    1. Drop all the tables from the DB: `docker exec -i [name of the DB container] psql postgres -U postgres -c "DROP DATABASE modulector;"`
-    1. Create an empty database: `docker exec -i [name of the DB container] psql postgres -U postgres -c "CREATE DATABASE modulector;"`
+    1. Drop all the tables from the DB: `docker exec -i [name of the DB container] psql postgres -U modulector -c "DROP DATABASE modulector;"`
+    1. Create an empty database: `docker exec -i [name of the DB container] psql postgres -U modulector -c "CREATE DATABASE modulector;"`
 1. Download `.sql.gz` from [Modulector releases pages](https://github.com/omics-datascience/modulector/releases) or use your own export file.
 1. Restore the database: `zcat modulector.sql.gz | docker exec -i [name of the DB container] psql modulector -U modulector`. This command will restore the database using a compressed dump as source, **keep in mind that could take several minutes to finish the process**.
    - **NOTE**: in case you are working on Windows, the command must be executed from [Git Bash][git-bash] or WSL.