Quickstart: Build and deploy a PHP web app to Cloud Run

Write the sample application

To write an application in PHP:

1. Create a new directory named helloworld-php and change directory into it:

   mkdir helloworld-php
   cd helloworld-php
   

2. Create a file named index.php and paste the following code into it:

   <?php
   
   $name = getenv('NAME', true) ?: 'World';
   echo sprintf('Hello %s!', $name);
   

   This code responds to requests with our "Hello World" greeting. HTTP handling is done by an Apache web server in the container.

3. Create a new file named Dockerfile in the same directory as the source files. The PHP Dockerfile starts an Apache web server that listens on the port defined by the PORT environment variable:

   
   # Use the official PHP image.
   # https://hub.docker.com/_/php
   FROM php:8.3-apache
   
   # Configure PHP for Cloud Run.
   # Precompile PHP code with opcache.
   RUN docker-php-ext-install -j "$(nproc)" opcache
   RUN set -ex; \
     { \
       echo "; Cloud Run enforces memory & timeouts"; \
       echo "memory_limit = -1"; \
       echo "max_execution_time = 0"; \
       echo "; File upload at Cloud Run network limit"; \
       echo "upload_max_filesize = 32M"; \
       echo "post_max_size = 32M"; \
       echo "; Configure Opcache for Containers"; \
       echo "opcache.enable = On"; \
       echo "opcache.validate_timestamps = Off"; \
       echo "; Configure Opcache Memory (Application-specific)"; \
       echo "opcache.memory_consumption = 32"; \
     } > "$PHP_INI_DIR/conf.d/cloud-run.ini"
   
   # Copy in custom code from the host machine.
   WORKDIR /var/www/html
   COPY . ./
   
   # Use the PORT environment variable in Apache configuration files.
   # https://cloud.google.com/run/docs/reference/container-contract#port
   RUN sed -i 's/80/${PORT}/g' /etc/apache2/sites-available/000-default.conf /etc/apache2/ports.conf
   
   # Configure PHP for development.
   # Switch to the production php.ini for production operations.
   # RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"
   # https://github.com/docker-library/docs/blob/master/php/README.md#configuration
   RUN mv "$PHP_INI_DIR/php.ini-development" "$PHP_INI_DIR/php.ini"
   

4. Add a .dockerignore file to exclude files from your container image.

   # The .dockerignore file excludes files from the container build process.
   #
   # https://docs.docker.com/engine/reference/builder/#dockerignore-file
   
   # Exclude locally vendored dependencies.
   vendor/
   
   # Exclude "build-time" ignore files.
   .dockerignore
   .gcloudignore
   
   # Exclude git history and configuration.
   .gitignore

Your app is finished and ready to be deployed.

Deploy to Cloud Run from source

Important: This quickstart assumes that you have owner or editor roles in the project you are using for the quickstart. Otherwise, refer to the Cloud Run Source Developer role for the required permissions for deploying a Cloud Run resource from source.

Deploy from source automatically builds a container image from source code and deploys it.

To deploy from source:

1. In your source code directory, deploy the current folder using the following command:

   gcloud run deploy --source .

   1. When you are prompted for the service name, press Enter to accept the default name, for example helloworld.

   2. If you are prompted to enable additional APIs on the project, for example, the Artifact Registry API, respond by pressing y.

   3. When you are prompted for region: select the region of your choice, for example us-central1.

   4. If you are prompted to create a repository in the specified region, respond by pressing y.

   5. If you are prompted to allow unauthenticated invocations: respond y. You might not see this prompt if there is a domain restriction organization policy that prevents it; for more details see the Before you begin section.

   Then wait a few moments until the deployment is complete. On success, the command line displays the service URL.

2. Visit your deployed service by opening the service URL in a web browser.

Congratulations! You have just deployed a container image from source code to Cloud Run. Cloud Run automatically and horizontally scales out your container image to handle the received requests, then scales in when demand decreases. You only pay for the CPU, memory, and networking consumed during request handling.