> ## Documentation Index > Fetch the complete documentation index at: https://planetscale.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Connect a PHP application to PlanetScale > In this tutorial, you'll learn how to connect a PHP application to a PlanetScale MySQL database with a sample PHP starter app using [MySQLi](https://www.php.net/manual/en/book.mysqli.php). Already have a PHP application and just want to connect to PlanetScale? Check out the [PHP quick connect repo](https://github.com/planetscale/connection-examples/tree/main/php). ## Prerequisites * [PHP](https://www.php.net/manual/en/install.php) — This tutorial uses `v8.1` * [Composer](https://getcomposer.org/) * A [PlanetScale account](https://auth.planetscale.com/sign-up) * [PlanetScale CLI](https://github.com/planetscale/cli) (Optional) — You can also follow this tutorial using just the PlanetScale admin dashboard, but the CLI will make setup quicker. ## Set up the PHP app This guide uses [a simple PHP app](https://github.com/planetscale/php-example) that displays a list of products stored in a PlanetScale database. If you have an existing application, you can also use that. PHP sample application homepage priority Clone the starter PHP application: ```bash theme={null} git clone https://github.com/planetscale/php-example.git ``` Enter into the folder and install the dependencies: ```bash theme={null} cd php-example composer install ``` Rename the `.env.example` file to `.env`: ```bash theme={null} mv .env.example .env ``` Start the application: ```bash theme={null} php -S localhost:8000 ``` You can view the application at [http://localhost:8000](http://localhost:8000). ## Set up the database Next, you need to set up your PlanetScale database and connect it to the PHP application. You can create a database either in the [PlanetScale dashboard](https://app.planetscale.com) or from the PlanetScale CLI. This guide will use the CLI, but you can follow the database setup instructions in the [PlanetScale quickstart guide](/vitess/tutorials/planetscale-quick-start-guide#create-a-database) if you prefer the dashboard. Just create the database and then come back here to continue. Install the [PlanetScale CLI](/cli/planetscale-environment-setup). Authenticate in the CLI with the following command: ```bash theme={null} pscale auth login ``` Create a new database with the following command: ```bash theme={null} pscale database create --region ``` You can use any name with lowercase, alphanumeric characters, or underscores. You can also use dashes, but we don't recommend them, as they may need to be escaped in some instances. For `REGION_SLUG`, choose a region closest to you from the [available regions](/vitess/regions#available-regions) or leave it blank. Your database is created with a default branch, `main`, which is meant to serve as your production database branch. That's it! Your database is ready to use. Next, let's connect it to the PHP application and then add some data. ## Connect to the PHP app There are **two ways to connect** to PlanetScale: * With an auto-generated username and password * Using the PlanetScale proxy with the CLI Both options are covered below. The environment variables you fill in next will be used in the [`db.php` file of the sample application](https://github.com/planetscale/php-example/blob/main/db.php): ```php theme={null} ssl_set(NULL, NULL, $ssl, NULL, NULL); $mysqli->real_connect($hostname, $username, $password, $dbName, $port); if ($mysqli->connect_error) { echo 'not connected to the database'; } else { echo "Connected successfully"; } ``` For `dbName`, you can use your PlanetScale database name directly if you have a *single unsharded keyspace*. If you have a sharded keyspace, you'll need to use `@primary`. This will automatically direct incoming queries to the correct keyspace/shard. For more information, see the [Targeting the correct keyspace documentation](/vitess/sharding/targeting-correct-keyspace). ### Option 1: Connect with username and password (Recommended) If you're not using the CLI, you can get the exact values to copy/paste from your PlanetScale dashboard. In the dashboard, select the branch you want to connect to from the infrastructure card (we're using `main`), click "**Connect**", and select "**PHP**" from the language dropdown. Copy these credentials, and then skip to step 2 to fill them in. Create a username and password with the PlanetScale CLI by running: ```bash theme={null} pscale password create ``` A default branch, `main`, was created when you created the database, so you can use that for `BRANCH_NAME`. The `PASSWORD_NAME` value represents the name of the username and password being generated. You can have multiple credentials for a branch, so this gives you a way to categorize them. To manage your passwords in the dashboard, go to your database dashboard page, click "Settings", and then click "Passwords". Take note of the values returned to you, as you won't be able to see this password again. Open the `.env` file in your PHP app: ```bash theme={null} HOST= DATABASE= USERNAME= PASSWORD= MYSQL_ATTR_SSL_CA= ``` Fill in your database name. For `USERNAME`, `PASSWORD`, and `HOST`, use the corresponding values from the CLI output. For `MYSQL_ATTR_SSL_CA`, use our [CA root configuration doc](/vitess/connecting/secure-connections#ca-root-configuration) to find the correct value for your system. For example, if you're on MacOS, it would be: ```bash theme={null} MYSQL_ATTR_SSL_CA=/etc/ssl/cert.pem ``` Refresh your PHP homepage, and you should see the message that you're connected to your database! ### Option 2: Connect with the PlanetScale proxy We recommend connecting with a username and password, but you can also open a quick connection with the PlanetScale proxy. You'll need the [PlanetScale CLI](https://github.com/planetscale/cli) for this option. Open a connection by running the following: ```bash theme={null} pscale connect ``` If you're following this guide exactly and haven't created any branches, you can use the default branch, `main`. A secure connection to your database will be established, and you'll see a local address you can use to connect to your application. Open the `.env` file in your PHP app and update it as follows: ```bash theme={null} HOST=127.0.0.1 PORT=3306 # Get this from the output of the previous step DATABASE= ``` The connection uses port `3306` by default, but we'll assign a random port if `3306` is in use. Make sure you paste in whatever port is returned in the terminal. Fill in the database name as well. Open `db.php` and replace it with the following: ```php expandable theme={null} ssl_set(NULL, NULL, $ssl, NULL, NULL); $mysqli->real_connect($hostname, '', '', $dbName, $port); if ($mysqli->connect_error) { echo 'not connected to the database'; } else { echo "Connected successfully"; } ``` This removes all references to `username`, `password`, and `ssl`. It's important to make sure that you add the SSL check back if you switch back to username and password credentials. We're intentionally commenting it out instead of deleting it in case you switch back. Refresh your PHP homepage, and you should see the message that you're connected to your database! ## Add the schema and data Now that you're connected to the database let's create the `products` and `categories` tables and add some data. There are a few ways to do this: * PlanetScale CLI shell * PlanetScale dashboard console * Your favorite MySQL client (for a list of tested MySQL clients, review our article on [how to connect MySQL GUI applications](/vitess/tutorials/connect-mysql-gui)) The first two options are covered below. ### Option 1: Add data with PlanetScale dashboard console If you don't care to install the MySQL client or the PlanetScale CLI, another quick option is using the MySQL console built into the PlanetScale dashboard. Go to your [PlanetScale dashboard](https://app.planetscale.com) and select your PHP database. On the "**Dashboard**" page, you will need to select the gear icon and demote your `main` branch by toggling the "Promote to production" option. This is so you can create tables directly on your `main` branch. Click on the "**Console**" and select the `main` branch (or whatever development branch you used). Create the `categories` table: ```sql theme={null} CREATE TABLE categories ( id INT AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL, description VARCHAR(255) NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB; ``` Create the `products` table: ```sql theme={null} CREATE TABLE products ( id INT AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL, description VARCHAR(255) NOT NULL, image VARCHAR(255) NOT NULL, category_id INT NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB; ``` If you are using foreign key constraints, you must first enable [foreign key constraints](/vitess/foreign-key-constraints) support in your database settings page. Add data to the `products` table with: ```sql theme={null} INSERT INTO `products` (name, description, image, category_id) VALUES ('Shoes', 'Description for Shoes', 'https://via.placeholder.com/150.png', '1'), ('Hat', 'Description for Hats', 'https://via.placeholder.com/150.png', '1'), ('Bicycle', 'Description for Bicycle', 'https://via.placeholder.com/150.png', '4'); ``` Add data to the `categories` table with: ```sql theme={null} INSERT INTO `categories` (name, description) VALUES ('Clothing', 'Description for Clothing'), ('Electronics', 'Description for Electronics'), ('Appliances', 'Description for Appliances'), ('Health', 'Description for Health'); ``` You can confirm that it was added by running: ```sql theme={null} SELECT * FROM products; SELECT * FROM categories; ``` You can now refresh the [PHP homepage](http://localhost:8000) to see the new record. ### Option 2: Add data with PlanetScale CLI You can use the PlanetScale CLI to open a MySQL shell to interact with your database. You may need to [install the MySQL command line client](/cli/planetscale-environment-setup) if you haven't already. Run the following command in your terminal: ```bash theme={null} pscale shell ``` This will open up a MySQL shell connected to the specified database and branch. A branch, `main`, was automatically created when you created your database, so you can use that for `BRANCH_NAME`. Create the `categories` table: ```sql theme={null} CREATE TABLE categories ( id INT AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL, description VARCHAR(255) NOT NULL ); ``` Create the `products` table: ```sql theme={null} CREATE TABLE products ( id int NOT NULL AUTO_INCREMENT PRIMARY KEY, name VARCHAR(255) NOT NULL, description VARCHAR(255) NOT NULL, image VARCHAR(255) NOT NULL, category_id INT NOT NULL, KEY category_id_idx (category_id) ); ``` Add some records to the `products` table: ```sql theme={null} INSERT INTO `products` (name, description, image, category_id) VALUES ('Shoes', 'Description for Shoes', 'https://via.placeholder.com/150.png', '1'), ('Hat', 'Description for Hats', 'https://via.placeholder.com/150.png', '1'), ('Bicycle', 'Description for Bicycle', 'https://via.placeholder.com/150.png', '4'); ``` The value `id` will be filled with a default value. Add some data to the `categories` table: ```sql theme={null} INSERT INTO `categories` (name, description) VALUES ('Clothing', 'Description for Clothing'), ('Electronics', 'Description for Electronics'), ('Appliances', 'Description for Appliances'), ('Health', 'Description for Health'); ``` You can verify everything was added in the PlanetScale CLI MySQL shell with: ```sql theme={null} SELECT * FROM products; SELECT * FROM categories; ``` Type `exit` to exit the shell. You can now refresh the [PHP homepage](http://localhost:8000) to see the new records. ## What's next? Once you're done with initial development, you can promote your branch to production and enable [safe migrations](/vitess/schema-changes/safe-migrations) on your `main` production branch to protect it against direct schema changes and enable zero-downtime schema migraions. When you're reading to make more schema changes, you'll [create a new branch](/vitess/schema-changes/branching) off of your production branch. Branching your database creates an isolated copy of your production schema so that you can easily test schema changes in development. Once you're happy with the changes, you'll [open a deploy request](/vitess/schema-changes/deploy-requests). This will generate a diff showing the changes that will be deployed, making it easy for your team to review. Learn more about how PlanetScale allows you to make [non-blocking schema changes](/vitess/schema-changes) to your database tables without locking or causing downtime for production databases. ## Need help? Get help from [the PlanetScale Support team](https://planetscale.com/contact?initial=support), or join our [Discord community](https://pscale.link/community) to see how others are using PlanetScale.