mirror of
https://github.com/Evolix/chexpire.git
synced 2024-05-02 08:50:49 +02:00
Document privilegies for test/dev user
They need to be able to create databases to execute tests in parallel.
This commit is contained in:
parent
d88f2f63b8
commit
4fbf2ddea0
|
@ -75,8 +75,8 @@ MariaDB [none]> CREATE DATABASE `chexpire_test`;
|
||||||
If you don't want to use the default `root` MySQL user with no password, you can create users :
|
If you don't want to use the default `root` MySQL user with no password, you can create users :
|
||||||
|
|
||||||
```
|
```
|
||||||
MariaDB [none]> GRANT ALL PRIVILEGES ON `chexpire_development`.* TO `chexpire_development`@localhost IDENTIFIED BY 'MY_PASSWORD_FOR_DEV';
|
MariaDB [none]> GRANT ALL PRIVILEGES ON `chexpire_development%`.* TO `chexpire_development`@localhost IDENTIFIED BY 'MY_PASSWORD_FOR_DEV';
|
||||||
MariaDB [none]> GRANT ALL PRIVILEGES ON `chexpire_test`.* TO `chexpire_test`@localhost IDENTIFIED BY 'MY_PASSWORD_FOR_TEST';
|
MariaDB [none]> GRANT ALL PRIVILEGES ON `chexpire_test%`.* TO `chexpire_test`@localhost IDENTIFIED BY 'MY_PASSWORD_FOR_TEST';
|
||||||
MariaDB [none]> FLUSH PRIVILEGES;
|
MariaDB [none]> FLUSH PRIVILEGES;
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
10
db/schema.rb
10
db/schema.rb
|
@ -2,11 +2,11 @@
|
||||||
# of editing this file, please use the migrations feature of Active Record to
|
# of editing this file, please use the migrations feature of Active Record to
|
||||||
# incrementally modify your database, and then regenerate this schema definition.
|
# incrementally modify your database, and then regenerate this schema definition.
|
||||||
#
|
#
|
||||||
# Note that this schema.rb definition is the authoritative source for your
|
# This file is the source Rails uses to define your schema when running `rails
|
||||||
# database schema. If you need to create the application database on another
|
# db:schema:load`. When creating a new database, `rails db:schema:load` tends to
|
||||||
# system, you should be using db:schema:load, not running all the migrations
|
# be faster and is potentially less error prone than running all of your
|
||||||
# from scratch. The latter is a flawed and unsustainable approach (the more migrations
|
# migrations from scratch. Old migrations may fail to apply correctly if those
|
||||||
# you'll amass, the slower it'll run and the greater likelihood for issues).
|
# migrations use external dependencies or application code.
|
||||||
#
|
#
|
||||||
# It's strongly recommended that you check this file into your version control system.
|
# It's strongly recommended that you check this file into your version control system.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue