Tethered local development

The simplest way to run a project locally is to use a local web server, but keep all other services on Platform.sh and connect to them over an SSH tunnel. This approach needs very little setup, but requires an active Internet connection, and depending on the speed of your connection and how I/O intensive your application is, it may not have suitable performance for day-to-day use.

Quick Start 

In your application directory run platform tunnel:open && export PLATFORM_RELATIONSHIPS="$(platform tunnel:info --encode)". This opens an SSH tunnel to your current Platform.sh environment and expose a local environment variable that mimics the relationships array on Platform.sh.

You can now run your application locally, assuming it’s configured to read its configuration from the Platform.sh environment variables.

Note that other Platform.sh environment configuration such as the routes or application secret value still aren’t available. Also be aware that the environment variable exists only in your current shell. If you are starting multiple local command shells you need to rerun the export command above in each of them.

Local web server 

For the local web server the approach varies depending on your language.

  • For a self-serving language (Go or Node.js), just run the program locally.
  • For PHP, you may install your own copy of Nginx (or Apache) and PHP-FPM, or just use the built-in PHP web server. Be aware that by default the PHP web server ignores environment variables by default. You need to explicitly instruct it to read them, like so: php -d variables_order=EGPCS -S localhost:8001. That starts a basic web server capable of running PHP, serving the current directory, on port 8001, using available environment variables. See the PHP manual for more information.
  • For other languages it’s recommended that you install your own copy of Nginx or Apache.
  • A virtual machine or Docker image is also a viable option.

SSH tunneling 

Now that the code is running, it needs to connect it to its services. For that, open an SSH tunnel to the current project.

$ platform tunnel:open
SSH tunnel opened on port 30000 to relationship: redis
SSH tunnel opened on port 30001 to relationship: database
Logs are written to: ~/.platformsh/tunnels.log

List tunnels with: platform tunnels
View tunnel details with: platform tunnel:info
Close tunnels with: platform tunnel:close

Now you can connect to the remote database normally, as if it were local.

$ mysql --host= --port=30001 --user='user' --password='' --database='main'

The specific port that each service uses isn’t guaranteed, but is unlikely to change unless you add an additional service or connect to multiple projects at once. In most cases it’s safe to add a local-configuration file for your application that connects to, in this case, localhost:30001 for the SQL database and localhost:30000 for Redis.

After the tunnels are opened, you can confirm their presence:

platform tunnel:list

You can show more information about the open tunnels with:

platform tunnel:info

and you can close tunnels with:

platform tunnel:close

Local environment variables 

Alternatively, you can read the relationship information directly from Platform.sh and expose it locally in the same form. From the command line, run:

export PLATFORM_RELATIONSHIPS="$(platform tunnel:info --encode)"

That creates a PLATFORM_RELATIONSHIPS environment variable locally that looks exactly the same as the one you’d see on Platform.sh, but pointing to the locally mapped SSH tunnels. Whatever code you have that looks for and decodes the relationship information from that variable (which is what runs on Platform.sh) detects it and uses it just as if you were running on Platform.sh.

Note that the environment variable is set globally so you can’t use this mechanism to load multiple tethered Platform.sh projects at the same time. If you need to run multiple tethered environments at once you have to read the relationships information for each one from the application code, like so:

if ($relationships_encoded = shell_exec('platform tunnel:info --encode')) {
    $relationships = json_decode(base64_decode($relationships_encoded, TRUE), TRUE);
    // ...
import json
import base64
import subprocess

encoded = subprocess.check_output(['platform', 'tunnel:info', '--encode'])
if (encoded):
    # ...
const child_process = require("child_process");

const { stdout: encoded } = child_process.spawnSync("platform", ["tunnel:info", "--encode"], { encoding : "utf8" });
const relationships = encoded ? JSON.parse(Buffer.from(encoded, "base64").toString()) : {};

// ...