@@ -2,56 +2,55 @@
22
33[](https://github.com/fabianlindfors/reshape/actions/workflows/test.yaml) [](https://github.com/fabianlindfors/reshape/releases)
44
5−> Also check out [ReshapeDB](https://reshapedb.com), a new database built from the ground up to make zero-downtime schema and data migrations as simple and safe as possible. If you'd like to chat about it, please [reach out](contact@reshapedb.com)!
6−
75Reshape is an easy-to-use, zero-downtime schema migration tool for Postgres. It automatically handles complex migrations that would normally require downtime or manual multi-step changes. During a migration, Reshape ensures both the old and new schema are available at the same time, allowing you to gradually roll out your application. It will also perform all changes without excessive locking, avoiding downtime caused by blocking other queries. For a more thorough introduction to Reshape, check out the [introductory blog post](https://fabianlindfors.se/blog/schema-migrations-in-postgres-using-reshape/).
86
97Designed for Postgres 12 and later.
108
9+*Note: Reshape is **experimental** and should not be used in production. It can (and probably will) break your application.*
10+
1111- [How it works](#how-it-works)
1212- [Getting started](#getting-started)
13− - [Installation](#installation)
14− - [Creating your first migration](#creating-your-first-migration)
15− - [Preparing your application](#preparing-your-application)
16− - [Running your migration](#running-your-migration)
17− - [Using during development](#using-during-development)
13+ - [Installation](#installation)
14+ - [Creating your first migration](#creating-your-first-migration)
15+ - [Preparing your application](#preparing-your-application)
16+ - [Running your migration](#running-your-migration)
17+ - [Using during development](#using-during-development)
1818- [Writing migrations](#writing-migrations)
19− - [Basics](#basics)
20− - [Tables](#tables)
21− - [Create table](#create-table)
22− - [Rename table](#rename-table)
23− - [Remove table](#remove-table)
24− - [Add foreign key](#add-foreign-key)
25− - [Remove foreign key](#remove-foreign-key)
26− - [Columns](#columns)
27− - [Add column](#add-column)
28− - [Alter column](#alter-column)
29− - [Remove column](#remove-column)
30− - [Indices](#indices)
31− - [Add index](#add-index)
32− - [Remove index](#remove-index)
33− - [Enums](#enums)
34− - [Create enum](#create-enum)
35− - [Remove enum](#remove-enum)
36− - [Custom](#custom)
37− - [Complex changes across tables](#complex-changes-across-tables)
19+ - [Basics](#basics)
20+ - [Tables](#tables)
21+ - [Create table](#create-table)
22+ - [Rename table](#rename-table)
23+ - [Remove table](#remove-table)
24+ - [Add foreign key](#add-foreign-key)
25+ - [Remove foreign key](#remove-foreign-key)
26+ - [Columns](#columns)
27+ - [Add column](#add-column)
28+ - [Alter column](#alter-column)
29+ - [Remove column](#remove-column)
30+ - [Indices](#indices)
31+ - [Add index](#add-index)
32+ - [Remove index](#remove-index)
33+ - [Enums](#enums)
34+ - [Create enum](#create-enum)
35+ - [Remove enum](#remove-enum)
3836- [Commands and options](#commands-and-options)
39− - [`reshape migration start`](#reshape-migration-start)
40− - [`reshape migration complete`](#reshape-migration-complete)
41− - [`reshape migration abort`](#reshape-migration-abort)
42− - [`reshape schema-query`](#reshape-schema-query)
43− - [Connection options](#connection-options)
37+ - [`reshape migrate`](#reshape-migrate)
38+ - [`reshape complete`](#reshape-complete)
39+ - [`reshape abort`](#reshape-abort)
40+ - [`reshape generate-schema-query`](#reshape-generate-schema-query)
41+ - [Connection options](#connection-options)
4442- [License](#license)
4543
44+
4645## How it works
4746
4847Reshape works by creating views that encapsulate the underlying tables, which your application will interact with. During a migration, Reshape will automatically create a new set of views and set up triggers to translate inserts and updates between the old and new schema. This means that every deployment is a three-phase process:
4948
50−1. **Start migration** (`reshape migration start`): Sets up views and triggers to ensure both the new and old schema are usable at the same time.
49+1. **Start migration** (`reshape migrate`): Sets up views and triggers to ensure both the new and old schema are usable at the same time.
51502. **Roll out application**: Your application can be gradually rolled out without downtime. The existing deployment will continue using the old schema whilst the new deployment uses the new schema.
52−3. **Complete migration** (`reshape migration complete`): Removes the old schema and any intermediate data and triggers.
51+3. **Complete migration** (`reshape complete`): Removes the old schema and any intermediate data and triggers.
5352
54−If the application deployment fails, you should run `reshape migration abort` which will roll back any changes made by `reshape migration start` without losing data.
53+If the application deployment fails, you should run `reshape abort` which will roll back any changes made by `reshape migrate` without losing data.
5554
5655## Getting started
5756
@@ -71,10 +70,10 @@ cargo install reshape
7170
7271#### Docker
7372
74−Reshape is available as a Docker image on [Docker Hub](https://hub.docker.com/repository/docker/fabianlindfors/reshape).
73+Reshape is available as a Docker image on [Docker Hub](https://hub.docker.com/repository/docker/fabianlindfors/reshape).
7574
7675```shell
77−docker run -v $(pwd):/usr/share/app fabianlindfors/reshape reshape migration start
76+docker run -v $(pwd):/usr/share/app fabianlindfors/reshape reshape migrate
7877```
7978
8079### Creating your first migration
@@ -103,14 +102,9 @@ This is the equivalent of running `CREATE TABLE users (id INTEGER GENERATED ALWA
103102
104103### Preparing your application
105104
106−Reshape relies on your application using a specific schema. When establishing the connection to Postgres in your application, you need to run a query to select the most recent schema. The simplest way to do this is to use one of the helper libraries:
107−
108−- [Rust](https://github.com/fabianlindfors/reshape-helper)
109−- [Ruby (and Rails)](https://github.com/fabianlindfors/reshape-ruby)
110−- [Python (and Django)](https://github.com/fabianlindfors/reshape-python)
111−- [Go](https://github.com/leourbina/reshape-helper)
105+Reshape relies on your application using a specific schema. When establishing the connection to Postgres in your application, you need to run a query to select the most recent schema. This query can be generated using: `reshape generate-schema-query`.
112106
113−If your application is not using one of the languages with an available helper library, you can instead generate the query with the command: `reshape schema-query`. To pass it along to your application, you can for example use an environment variable in your run script: `RESHAPE_SCHEMA_QUERY=$(reshape schema-query)`. Then in your application:
107+To pass it along to your application, you can for example use an environment variable in your run script: `RESHAPE_SCHEMA_QUERY=$(reshape generate-schema-query)`. Then in your application:
114108
115109```python
116110# Example for Python
@@ -123,16 +117,16 @@ db.execute(reshape_schema_query)
123117To create your new `users` table, run:
124118
125119```bash
126−reshape migration start --complete
120+reshape migrate --complete
127121```
128122
129−We use the `--complete` flag to automatically complete the migration. During a production deployment, you should first run `reshape migration start` followed by `reshape migration complete` once your application has been fully rolled out.
123+We use the `--complete` flag to automatically complete the migration. During a production deployment, you should first first run `reshape migrate` followed by `reshape complete` once your application has been fully rolled out.
130124
131125If nothing else is specified, Reshape will try to connect to a Postgres database running on `localhost` using `postgres` as both username and password. See [Connection options](#connection-options) for details on how to change the connection settings.
132126
133127### Using during development
134128
135−When adding new migrations during development, we recommend running `reshape migration start` but skipping `reshape migration complete`. This way, the new migrations can be iterated on by updating the migration file and running `reshape migration abort` followed by `reshape migration start`.
129+When adding new migrations during development, we recommend running `reshape migrate` but skipping `reshape complete`. This way, the new migrations can be iterated on by updating the migration file and running `reshape abort` followed by `reshape migrate`.
136130
137131## Writing migrations
138132
@@ -167,9 +161,9 @@ Every action has a `type`. The supported types are detailed below.
167161
168162#### Create table
169163
170−The `create_table` action will create a new table with the specified columns, indices and constraints. You can optionally provide an `up` option to backfill values from an existing table.
164+The `create_table` action will create a new table with the specified columns, indices and constraints.
171165
172−_Example: create a `customers` table with a few columns and a primary key_
166+*Example: create a `customers` table with a few columns and a primary key*
173167
174168```toml
175169[[actions]]
@@ -187,13 +181,13 @@ primary_key = ["id"]
187181 type = "TEXT"
188182
189183 # Columns default to nullable
190− nullable = false
184+ nullable = false
191185
192186 # default can be any valid SQL value, in this case a string literal
193− default = "'PLACEHOLDER'"
187+ default = "'PLACEHOLDER'"
194188```
195189
196−_Example: create `users` and `items` tables with a foreign key between them_
190+*Example: create `users` and `items` tables with a foreign key between them*
197191
198192```toml
199193[[actions]]
@@ -226,34 +220,11 @@ primary_key = ["id"]
226220 referenced_columns = ["id"]
227221```
228222
229−_Example: create `profiles` table based on existing `users` table_
230−
231−```toml
232−[[actions]]
233−type = "create_table"
234−name = "profiles"
235−primary_key = ["user_id"]
236−
237− [[actions.columns]]
238− name = "user_id"
239− type = "INTEGER"
240−
241− [[actions.columns]]
242− name = "user_email"
243− type = "TEXT"
244−
245− # Backfill from `users` table and copy `users.email` to `user_email` column
246− # This will perform an upsert based on the primary key to avoid duplicate rows
247− [actions.up]
248− table = "users"
249− values = { user_id = "id", user_email = "email" }
250−```
251−
252223#### Rename table
253224
254225The `rename_table` action will change the name of an existing table.
255226
256−_Example: change name of `users` table to `customers`_
227+*Example: change name of `users` table to `customers`*
257228
258229```toml
259230[[actions]]
@@ -266,7 +237,7 @@ new_name = "customers"
266237
267238The `remove_table` action will remove an existing table.
268239
269−_Example: remove `users` table_
240+*Example: remove `users` table*
270241
271242```toml
272243[[actions]]
@@ -278,7 +249,7 @@ table = "users"
278249
279250The `add_foreign_key` action will add a foreign key between two existing tables. The migration will fail if the existing column values aren't valid references.
280251
281−_Example: create foreign key from `items` to `users` table_
252+*Example: create foreign key from `items` to `users` table*
282253
283254```toml
284255[[actions]]
@@ -295,7 +266,7 @@ table = "items"
295266
296267The `remove_foreign_key` action will remove an existing foreign key. The foreign key will only be removed once the migration is completed, which means that your new application must continue to adhere to the foreign key constraint.
297268
298−_Example: remove foreign key `items_user_id_fkey` from `users` table_
269+*Example: remove foreign key `items_user_id_fkey` from `users` table*
299270
300271```toml
301272[[actions]]
@@ -308,9 +279,9 @@ foreign_key = "items_user_id_fkey"
308279
309280#### Add column
310281
311−The `add_column` action will add a new column to an existing table. You can optionally provide an `up` setting. This should be an SQL expression which will be run for all existing rows to backfill the new column. `up` may also reference another table to perform cross-table migrations (see ["Complex changes across tables"](#complex-changes-across-tables)).
282+The `add_column` action will add a new column to an existing table. You can optionally provide an `up` setting. This should be an SQL expression which will be run for all existing rows to backfill the new column.
312283
313−_Example: add a new column `reference` to table `products`_
284+*Example: add a new column `reference` to table `products`*
314285
315286```toml
316287[[actions]]
@@ -324,7 +295,7 @@ table = "products"
324295 default = "10"
325296```
326297
327−_Example: replace an existing `name` column with two new columns, `first_name` and `last_name`_
298+*Example: replace an existing `name` column with two new columns, `first_name` and `last_name`*
328299
329300```toml
330301[[actions]]
@@ -360,7 +331,7 @@ column = "name"
360331down = "first_name || ' ' || last_name"
361332```
362333
363−_Example: extract nested value from unstructured JSON `data` column to new `name` column_
334+*Example: extract nested value from unstructured JSON `data` column to new `name` column*
364335
365336```toml
366337[[actions]]
@@ -375,33 +346,14 @@ up = "data['path']['to']['value'] #>> '{}'"
375346 type = "TEXT"
376347```
377348
378−_Example: duplicate `email` column from `users` to `profiles` table_
379−
380−```toml
381−# `profiles` has `user_id` column which maps to `users.id`
382−[[actions]]
383−type = "add_column"
384−table = "profiles"
385−
386− [actions.column]
387− name = "email"
388− type = "TEXT"
389− nullable = false
390−
391− # When `users` is updated in the old schema, we write the email value to `profiles`
392− [actions.up]
393− table = "users"
394− value = "email"
395− where = "user_id = id"
396−```
397349
398350#### Alter column
399351
400352The `alter_column` action enables many different changes to an existing column, for example renaming, changing type and changing existing values.
401353
402−When performing more complex changes than a rename, `up` and `down` should be provided. These should be SQL expressions which determine how to transform between the new and old version of the column. Inside those expressions, you can reference the current column value by the column name.
354+When performing more complex changes than a rename, `up` and `down` must be provided. These should be SQL expressions which determine how to transform between the new and old version of the column. Inside those expressions, you can reference the current column value by the column name.
403355
404−_Example: rename `last_name` column on `users` table to `family_name`_
356+*Example: rename `last_name` column on `users` table to `family_name`*
405357
406358```toml
407359[[actions]]
@@ -413,7 +365,7 @@ column = "last_name"
413365 name = "family_name"
414366```
415367
416−_Example: change the type of `reference` column from `INTEGER` to `TEXT`_
368+*Example: change the type of `reference` column from `INTEGER` to `TEXT`*
417369
418370```toml
419371[[actions]]
@@ -428,7 +380,7 @@ down = "CAST(reference AS INTEGER)" # Converts from text value to integer
428380 type = "TEXT" # Previous type was 'INTEGER'
429381```
430382
431−_Example: increment all values of an `index` column by one_
383+*Example: increment all values of an `index` column by one*
432384
433385```toml
434386[[actions]]
@@ -443,22 +395,7 @@ down = "index - 1" # Decrement to revert for old schema
443395 name = "index"
444396```
445397
446−_Example: make `name` column not nullable_
447−
448−```toml
449−[[actions]]
450−type = "alter_column"
451−table = "users"
452−column = "name"
453−
454−# Use "N/A" for any rows that currently have a NULL name
455−up = "COALESCE(name, 'N/A')"
456−
457− [actions.changes]
458− nullable = false
459−```
460−
461−_Example: change default value of `created_at` column to current time_
398+*Example: change default value of `created_at` column to current time*
462399
463400```toml
464401[[actions]]
@@ -472,11 +409,11 @@ column = "created_at"
472409
473410#### Remove column
474411
475−The `remove_column` action will remove an existing column from a table. You can optionally provide a `down` setting. This should be an SQL expression which will be used to determine values for the old schema when inserting or updating rows using the new schema. `down` may also reference another table to perform cross-table migrations (see ["Complex changes across tables"](#complex-changes-across-tables)) . The `down` setting must be provided when the removed column is `NOT NULL` or doesn't have a default value.
412+The `remove_column` action will remove an existing column from a table. You can optionally provide a `down` setting. This should be an SQL expression which will be used to determine values for the old schema when inserting or updating rows using the new schema. The `down` setting must be provided when the removed column is `NOT NULL` or doesn't have a default value.
476413
477414Any indices that cover the column will be removed.
478415
479−_Example: remove column `name` from table `users`_
416+*Example: remove column `name` from table `users`*
480417
481418```toml
482419[[actions]]
@@ -488,34 +425,18 @@ column = "name"
488425down = "'N/A'"
489426```
490427
491−_Example: remove `email` column from `users` table and use column from `profiles` table instead_
492−
493−```toml
494−[[actions]]
495−type = "remove_column"
496−table = "users"
497−column = "email"
498−
499− # Our application will use the `profiles.email` column instead
500− # For backwards compatibility, we will write back to the removed `email` column whenever `profiles` is changed
501− [actions.down]
502− table = "profiles"
503− value = "profiles.email"
504− where = "users.id = profiles.user_id"
505−```
506−
507428### Indices
508429
509430#### Add index
510431
511432The `add_index` action will add a new index to an existing table.
512433
513−_Example: create a `users` table with a unique index on the `name` column_
434+*Example: create a `users` table with a unique index on the `name` column*
514435
515436```toml
516437[[actions]]
517438type = "create_table"
518−name = "users"
439+table = "users"
519440primary_key = "id"
520441
521442 [[actions.columns]]
@@ -539,7 +460,7 @@ table = "users"
539460 unique = true
540461```
541462
542−_Example: add GIN index to `data` column on `products` table_
463+*Example: add GIN index to `data` column on `products` table*
543464
544465```toml
545466[[actions]]
@@ -558,7 +479,7 @@ table = "products"
558479
559480The `remove_index` action will remove an existing index. The index won't actually be removed until the migration is completed.
560481
561−_Example: remove the `name_idx` index_
482+*Example: remove the `name_idx` index*
562483
563484```toml
564485[[actions]]
@@ -572,7 +493,7 @@ index = "name_idx"
572493
573494The `create_enum` action will create a new [enum type](https://www.postgresql.org/docs/current/datatype-enum.html) with the specified values.
574495
575−_Example: add a new `mood` enum type with three possible values_
496+*Example: add a new `mood` enum type with three possible values*
576497
577498```toml
578499[[actions]]
@@ -585,7 +506,7 @@ values = ["happy", "ok", "sad"]
585506
586507The `remove_enum` action will remove an existing [enum type](https://www.postgresql.org/docs/current/datatype-enum.html). Make sure all usages of the enum has been removed before running the migration. The enum will only be removed once the migration is completed.
587508
588−_Example: remove the `mood` enum type_
509+*Example: remove the `mood` enum type*
589510
590511```toml
591512[[actions]]
@@ -593,178 +514,61 @@ type = "remove_enum"
593514enum = "mood"
594515```
595516
596−### Custom
597−
598−The `custom` action lets you create a migration which runs custom SQL. It should be used with great care as it provides no guarantees of zero-downtime and will simply run whatever SQL is provided. Use other actions whenever possible as they are explicitly designed for zero downtime.
599−
600−There are three optional settings available which all accept SQL queries. All queries need to be idempotent, for example by using `IF NOT EXISTS` wherever available.
601−
602−- `start`: run when a migration is started using `reshape migration start`
603−- `complete`: run when a migration is completed using `reshape migration complete`
604−- `abort`: run when a migration is aborted using `reshape migration abort`
605−
606−_Example: enable PostGIS and pg_stat_statements extensions_
607−
608−```toml
609−[[actions]]
610−type = "custom"
611−
612−start = """
613− CREATE EXTENSION IF NOT EXISTS postgis;
614− CREATE EXTENSION IF NOT EXISTS pg_stat_statements;
615−"""
616−
617−abort = """
618− DROP EXTENSION IF EXISTS postgis;
619− DROP EXTENSION IF EXISTS pg_stat_statements;
620−"""
621−```
622−
623−### Complex changes across tables
624−
625−The `up` and `down` options available when creating tables, adding columns and removing columns can also perform more complex changes that span tables.
626−
627−_Example: move `email` column from `users` to `profiles` table_
628−
629−```toml
630−[[actions]]
631−type = "add_column"
632−table = "profiles"
633−
634− [actions.column]
635− name = "email"
636− type = "TEXT"
637− nullable = false
638−
639− # When `users` is updated in the old schema, we write the email value to `profiles`
640− [actions.up]
641− table = "users"
642− value = "users.email"
643− where = "profiles.user_id = users.id"
644−
645−[[actions]]
646−type = "remove_column"
647−table = "users"
648−column = "email"
649−
650− # When `profiles` is changed in the new schema, we write the email address back to the removed column
651− [actions.down]
652− table = "profiles"
653− value = "profiles.email"
654− where = "users.id = profiles.user_id"
655−```
656−
657−_Example: turn a 1:N relationship between `users` and `accounts` into N:M and change the format of the associated `role`_
658−
659−```toml
660−# Add `user_account_connections` as a junction table
661−[[actions]]
662−type = "create_table"
663−name = "user_account_connections"
664−primary_key = ["account_id", "user_id"]
665−
666− [[actions.columns]]
667− name = "account_id"
668− type = "INTEGER"
669−
670− [[actions.columns]]
671− name = "user_id"
672− type = "INTEGER"
673−
674− # `role` is currently stored directly on the `users` table but is part of the relationship
675− [[actions.columns]]
676− name = "role"
677− type = "TEXT"
678− nullable = false
679−
680− # Backfill the new table from `users` and uppercase the `role`
681− [actions.up]
682− table = "users"
683− values = { user_id = "id", account_id = "account_id", role = "UPPER(account_role)" }
684− where = "user_account_connections.user_id = users.id"
685−
686−[[actions]]
687−type = "remove_column"
688−table = "users"
689−column = "account_id"
690−
691− # When `user_account_connections` is updated, we write the `account_id` back to `users`
692− [actions.down]
693− table = "user_account_connections"
694− value = "user_account_connections.account_id"
695− where = "users.id = user_account_connections.user_id"
696−
697−[[actions]]
698−type = "remove_column"
699−table = "users"
700−column = "account_role"
701−
702− # When `user_account_connections` is updated, we write the lowercase role back to `users`
703− [actions.down]
704− table = "user_account_connections"
705− value = "LOWER(user_account_connections.role)"
706− where = "users.id = user_account_connections.user_id"
707−```
708−
709517## Commands and options
710518
711−### `reshape migration start`
519+### `reshape migrate`
712520
713−Starts a new migration, applying all migrations under `migrations/` that haven't yet been applied. After the command has completed, both the old and new schema will be usable at the same time. When you have rolled out the new version of your application which uses the new schema, you should run `reshape migration complete`.
521+Starts a new migration, applying all migrations under `migrations/` that haven't yet been applied. After the command has completed, both the old and new schema will be usable at the same time. When you have rolled out the new version of your application which uses the new schema, you should run `reshape complete`.
714522
715523#### Options
716524
717−_See also [Connection options](#connection-options)_
525+*See also [Connection options](#connection-options)*
718526
719−| Option | Default | Description |
720−| ------------------ | ------------- | --------------------------------------------------------------------------------------------------------------- |
721−| `--complete`, `-c` | `false` | Automatically complete migration after applying it. |
722−| `--dirs` | `migrations/` | Directories to search for migration files. Multiple directories can be specified using `--dirs dir1 dir2 dir3`. |
527+| Option | Default | Description |
528+| ------ | ------- | ----------- |
529+| `--complete`, `-c` | `false` | Automatically complete migration after applying it. |
530+| `--dirs` | `migrations/` | Directories to search for migration files. Multiple directories can be specified using `--dirs dir1 dir2 dir3`. |
723531
724−### `reshape migration complete`
532+### `reshape complete`
725533
726−Completes migrations previously started with `reshape migration complete`.
534+Completes migrations previously started with `reshape complete`.
727535
728536#### Options
729537
730538See [Connection options](#connection-options)
731539
732−### `reshape migration abort`
540+### `reshape abort`
733541
734−Aborts any migrations which haven't yet been completed.
542+Aborts any migrations which haven't yet been completed.
735543
736544#### Options
737545
738546See [Connection options](#connection-options)
739547
740−### `reshape schema-query`
548+### `reshape generate-schema-query`
741549
742550Generates the SQL query you need to run in your application before using the database. This command does not require a database connection. Instead it will generate the query based on the latest migration in the `migrations/` directory (or the directories specified by `--dirs`).
743551
744−If your application is written in Rust, we recommend using the [Rust helper library](https://github.com/fabianlindfors/reshape-helper/) instead.
745−
746552The query should look something like `SET search_path TO migration_1_initial_migration`.
747553
748554#### Options
749555
750−| Option | Default | Description |
751−| -------- | ------------- | --------------------------------------------------------------------------------------------------------------- |
556+| Option | Default | Description |
557+| ------ | ------- | ----------- |
752558| `--dirs` | `migrations/` | Directories to search for migration files. Multiple directories can be specified using `--dirs dir1 dir2 dir3`. |
753559
754560### Connection options
755561
756−The options below can be used with all commands that communicate with Postgres. Use either a [connection URL](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING) or specify each connection option individually.
757−
758−All options can also be set using environment variables instead of flags. If a `.env` file exists, then variables will be automatically loaded from there.
562+The options below can be used with all commands that communicate with Postgres. Use either a connection URL or specify each connection option individually.
759563
760−| Option | Default | Environment variable | Description |
761−| ------------ | ----------- | -------------------- | ------------------------------------------- |
762−| `--url` | | `DB_URL` | URL to your Postgres database |
763−| `--host` | `localhost` | `DB_HOST` | Hostname to use when connecting to Postgres |
764−| `--port` | `5432` | `DB_PORT` | Port which Postgres is listening on |
765−| `--database` | `postgres` | `DB_NAME` | Database name |
766−| `--username` | `postgres` | `DB_USERNAME` | Postgres username |
767−| `--password` | `postgres` | `DB_PASSWORD` | Postgres password |
564+| Option | Default | Description |
565+| ------ | ------- | ----------- |
566+| `--url` | | URI to connect to your Postgres database.<br>Can also be provided with the environment variable `DATABASE_URL`. |
567+| `--host` | `localhost` | Hostname to use when connecting to Postgres |
568+| `--port` | `5432` | Port which Postgres is listening on |
569+| `--database` | `postgres` | Database name |
570+| `--username` | `postgres` | Postgres username |
571+| `--password` | `postgres` | Postgres password |
768572
769573## License
770574