Run composer create-project roots/bedrock dev-master (path being the folder to install to)
Edit .env and update environment variables:
DB_NAME=test2
DB_USER=
DB_PASSWORD=
DB_HOST=localhost
The install page sets up the database with the records that WordPress needs to run; a blank database is not sufficient. Either complete the install there or look into WP-CLI to do it from the command line.
How did you show clients your work previously? A staging server? Nothing should change in that respect except that you’re using Bedrock to power it.
If the credentials are right, you’ll need to change the DB_HOST to match your setup. If you’re on Windows then you’ll have to search online to figure out how to do this.
For Unix-like systems you should be able to use: lsof -i4 -P | grep -i mysql in the terminal. The final column will be the IP and the port you need.
I’m guessing when you said FTP, you meant you FTP’d the site to a staging server and your clients would view the site through there. Bedrock will not change this. You could set things up locally to allow the client to connect directly to your local machine but this is almost always a bad idea.
Bedrock envisioned three environments. A local server for development (i.e. your own machine), an external staging server for review/testing and an external production server for the finished app.
When developing locally, it should only be you who has access. There is no need for FTP as it’s the local files that are being served.
When you have a site ready for review, you commit and push your changes and can deploy to the staging server via Capistrano. You then do the same again for the production server, when the app is good to go. At no point is FTP required.