3.2 A project's database

Creating the database and user

The section has one part for MySQL and one for MongoDB (with “used by the project” if the kit sees that the project uses it). If the project uses SQLite, a note explains that the database is a file of the project and no server is needed.

1. Press “Create database and user” in the part of the server you need.
2. The kit installs and starts the server if needed, then creates a database and a user with the project's name (lowercase letters, digits and underscore: gestionale-fatture becomes gestionale_fatture) and a 32-character password.
3. The part shows “Database”, “User”, “Password” and “String” (hidden, with “Show” and “Copy”) and “Address”.

Writing the connection to the .env file

1. Press “Write to .env”.
2. “Lines of .env that change” appears: for each key, the old value crossed out and the new one (passwords hidden).
3. Press “Write” to confirm, or “Cancel”.

The kit chooses the keys based on your .env file:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=gestionale
DB_USERNAME=gestionale
DB_PASSWORD=3f9c…(32 characters generated by the kit)

DATABASE_URL=mysql://portale:3f9c…@127.0.0.1:3306/portale
MONGODB_URI=mongodb://portale:a71e…@127.0.0.1:27017/portale?authSource=portale

• If the .env file does not exist, it is created by copying .env.example. The other lines and the comments stay.
• If the connection is already the right one: “The .env file already has this connection.”
• “Copy .env block”, next to it, does not touch the file: it copies the lines of the table (DB_* for Laravel, otherwise DATABASE_URL or MONGODB_URI) to paste into another .env, a configuration file or a terminal; “Copied” appears. The lines contain the password: the kit reads them only when you press the button.

Copies and restore

1. In the “Copies” part press “Export”: “Copy saved: …” appears and the copy is added to the list.
2. To go back to a copy, press “Restore…” next to the file and confirm: “The current data is replaced.”
3. Before restoring, the kit copies what the database holds now, into <database>-prima-del-ripristino-<date and time>: if the copy fails, the restore is not done. So a restore of the wrong file is undone by restoring that copy.
4. “Open the copies folder” opens the folder: to restore a copy that came from outside (from a colleague, from another kit), put it there and it will appear in the list.

Of the safety copies (“prima-del-ripristino” and “prima-del-cambio-di-versione”) the kit keeps the last 3 of each kind and deletes the older ones. The copies made with “Export” are never deleted.

Changing the server version

If you have several versions of MySQL or MongoDB, the “Server version” menu chooses which one the project's database runs on. When you change it, the database and user are also created on the new version, empty: you carry the data over with a copy (Export on the old one, Restore on the new one). If the chosen version is not installed, “Install …” appears. Before the change the kit copies the database on the version it leaves, into <database>-prima-del-cambio-di-versione-<date and time>: if the copy fails, the version does not change (if that version is no longer installed, there is nothing to copy and the change goes ahead).