Skip to content

Updates to Platform.sh deploy instructions #8397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

pjcdawkins
Copy link

@pjcdawkins pjcdawkins commented Sep 15, 2017

  • Update example PHP version from 5.6 to 7.1
  • Files in .platform are now required
  • Endpoint name php is better written as http
  • Build flavor symfony is better written as composer
  • Rename database from mysql to mydatabase to separate it clearly from the service type
  • The web section should now use locations
  • Use SSL by default (certificate provisioning and 'http://' redirects are automatic)

There are probably additional improvements that can be made, referring to the Platform.sh documentation and to the work that has been done in https://github.com/platformsh/platformsh-example-symfony/

* Update example PHP version from 5.6 to 7.1
* Files in `.platform` are now required
* Endpoint name `php` is better written as `http`
* Build flavor `symfony` is better written as `composer`
* Rename database from `mysql` to `mydatabase` to separate it clearly from the service type
* The `web` section should now use `locations`
build:
flavor: symfony
flavor: composer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do you change this? symfony is correct

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I read somewhere that composer is the new and recommended type for all PHP. Their Symfony template doc use that too: https://docs.platform.sh/frameworks/symfony.html

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good to know, thank you @javiereguiluz 👍

type: upstream
# the first part should be your project name
upstream: 'myphpproject:php'
upstream: 'myphpproject:http'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be:

'https://{default}/':
  type: upstream
  upstream: "myphpproject:http"
'https://www.{default}/':
  type: redirect
  to: "https://{default}/"

@OskarStark
Copy link
Contributor

Refs #8483

@@ -73,21 +75,21 @@ Platform.sh how to deploy your application (read more about
deploy: |
bin/console --env=prod cache:clear

For best practices, you should also add a ``.platform`` folder at the root of
You also need add a ``.platform`` folder at the root of
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to add

@javiereguiluz
Copy link
Member

@pjcdawkins thanks for this contribution, but sadly we must close this pull request without merging it. Why? Because in #8721 we decided to remove all these articles explaining how to deploy to third-party services. We now simply link to the articles published by those services. Thanks for understanding it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants