If you have been customizing your existing project as you go, now is the time to ensure all code is committed to Git and to run
git push to Platform.sh to your production branch. Platform.sh then builds your code, producing a read-only image of your application, and deploys it into a running cluster of containers.
You can view the process in the console or, if you aren't using a source integration, in your terminal after pushing. When the process is done, click the URL to see your site.
If you set up an integration to a repository that contained many pull requests with the
–build-pull-requests=false flag, you can now activate the current environment to complete your deployment.
$ platform environment:activate -e <ENVIRONMENT_NAME>
A standard Gatsby site - either one created interactively through npm (
npm init gatsby) or through a starter such as the Blog starter used in the Platform.sh template - will generate a static site without the use of any external services. If this is your starting point you have all of the configuration necessary to deploy your project, but below are a few modifications that may help you develop your site more efficiently going forward.
Platform.sh provides all information about the running environment, including how to connect to services, through environment variables. These may be accessed directly, but it’s often easier to use the Platform.sh Config Reader library. It’s a set of utilities to wrap the environment variables and make them a bit more ergonomic to work with.
npm install platformsh-config # Or for Yarn yarn add platformsh-config
Go forth and Deploy (even on Friday)!