more lift renaming

prisma · Jan 20, 2020 · 2d4780d · 2d4780d
1 parent e6170b0
commit 2d4780d
Show file tree

Hide file tree

Showing 6 changed files with 16 additions and 14 deletions.
diff --git a/docs/README.md b/docs/README.md
@@ -18,7 +18,7 @@
   - [Use only Prisma Client JS](./prisma-client-js/use-only-prisma-client-js.md)
   - [Code generation & Node.js setup](./prisma-client-js/codegen-and-node-setup.md)
   - [Deployment](./prisma-client-js/deployment.md)
-- [Lift](./lift)
+- [Prisma Migrate](./prisma-migrate)
 - [Importing and exporting data](./import-and-export-data)
 - [Supported databases](./supported-databases.md)
 - [Telemetry](./telemetry.md)

diff --git a/docs/migrations/README.md b/docs/migrations/README.md
diff --git a/docs/prisma-client-js/use-only-prisma-client-js.md b/docs/prisma-client-js/use-only-prisma-client-js.md
@@ -1,10 +1,10 @@
-# Using only Prisma Client JS (without Lift)
+# Using only Prisma Client JS (without Prisma Migrate)
 
-You can use Prisma Client JS as an ORM replacement in your application without using Lift for database migrations. This is useful for _existing applications_ when there already is a working migration system or when you don't have the rights inside your organization to perform database migrations yourself.
+You can use Prisma Client JS as an ORM replacement in your application without using Prisma for database migrations. This is useful for _existing applications_ when there already is a working migration system or when you don't have the rights inside your organization to perform database migrations yourself.
 
-When using Prisma Client JS without Lift, you obtain your data model definition by _introspecting_ your database schema and generating the Prisma data model from it. The generated data model then serves as foundation for Prisma Client JS's generated CRUD API. Whenever a schema migration is performed on the database afterwards, you need to re-introspect your database (which updates your data model) and re-generate your Prisma Client JS API.
+When using Prisma Client JS without migrations, you obtain your data model definition by _introspecting_ your database schema and generating the Prisma data model from it. The generated data model then serves as foundation for Prisma Client JS's generated CRUD API. Whenever a schema migration is performed on the database afterwards, you need to re-introspect your database (which updates your data model) and re-generate your Prisma Client JS API.
 
-**This page is about using Prisma Client JS with an existing database**. Learn more about getting started from scratch with Prisma Client JS and Lift [here](./).
+**This page is about using Prisma Client JS with an existing database**. Learn more about getting started from scratch with Prisma [here](./).
 
 ## Getting started with Prisma Client JS
 

diff --git a/docs/prisma-migrate/README.md b/docs/prisma-migrate/README.md
@@ -0,0 +1,8 @@
+# Prisma Migrate
+
+This directory contains the documentation for the Prisma Migrate, the Prisma Framework's schema migration tool. To learn more about the respective CLI commands, check out the docs for the [Prisma Framework CLI](../prisma2-cli.md).
+
+> ⚠️ Prisma's migration functionality is currently in an **experimental** state. When using any of the commands below, you need to explicitly opt-in to that functionality via an `--experimental` flag that needs to be passed to a command, e.g. `prisma2 migrate save --name 'init' --experimental`
+
+- [Migration files](./migration-files.md)
+- [Use only Migrate](./use-only-migrate.md)
diff --git a/docs/migrations/migration-files.md → docs/prisma-migrate/migration-files.md b/docs/migrations/migration-files.md → docs/prisma-migrate/migration-files.md
diff --git a/docs/prisma2-feedback.md b/docs/prisma2-feedback.md
@@ -14,7 +14,7 @@ For that, a full rewrite of Prisma was necessary so that we can build upon a pro
 - Track the progress of the Prisma Framework here: [`isprisma2ready.com`](https://www.isprisma2ready.com)
 - Open issues in following repos:
   - General Prisma Framework questions and catch-all for problems and questions: [`prisma2`](https://github.com/prisma/prisma2)
-  - Problems/questions regarding Lift: [`lift`](https://github.com/prisma/lift)
+  - Problems/questions regarding Prisma Migrate: [`lift`](https://github.com/prisma/lift)
   - Problems/questions regarding Prisma Client JS: [`prisma-client-js`](https://github.com/prisma/prisma-client-js)
 
 ## Your opinion matters – a lot!
@@ -46,10 +46,10 @@ In any of the following scenarios, please make sure to create a GitHub issue to
 - The documentation on something isn't clear.
 - You wish there was documentation on something.
 
-If your issue relates to either Prisma Client JS or Lift specifically, you can open an issue directly in the respective repositories:
+If your issue relates to either Prisma Client JS or Prisma Migrate specifically, you can open an issue directly in the respective repositories:
 
 - [Open an issue for **Prisma Client JS**](https://github.com/prisma/prisma-client-js/issues/new)
-- [Open an issue for **Lift**](https://github.com/prisma/lift/issues/new)
+- [Open an issue for **Prima Migrate**](https://github.com/prisma/lift/issues/new)
 
 Otherwise, the default place for opening issues is the official `prisma2` repo (when in doubt, create the issue here):