Implement support and automated tests using key platform templates

[rfay]

It is time to return to the automated tests, preferably trying to do something live.

[rfay]

• Platform templates are at https://github.com/platformsh-templates
• Spreadsheet showing usage - with PHP highlighted.

[rfay]

Here are Platform's template priorities

[rfay]

Another source for prioritization is Product Area: Product Experience - Top Level Vision, Strategy & 2023 goals

Tech Stacks:
Drupal (CMS)
Wordpress (CMS)
Magento (CMS)
Laravel (Framework)
Symfony (Framework)

[rfay]

@gilzow for our strategies coming up, could you suggest what the best way to work through maybe 4 of them could be?

It looks to me like we have decent tests for Drupal and wordpress-bedrock. The WP Bedrock has a database, so better tests, I'll add a database to Drupal 9.

We have a test for laravel, which means that it seemed to work when I tried it, but it doesn't have a database.

Does that mean that magento2ce and Symfony would be our next targets?

[gilzow]

Some others we can/should test:
Pimcore
Typo3

As for priorities, I think you're right: symfony and magento should be next.

[rfay]

Sounds good. I'm scared of pimcore, as the only round I've had with it had all kinds of crazy stuff in it. TYPO3 should work out fine.

[rfay]

So priorities for coming weeks:

• Magento2ce (requires routes processing, Improve $PLATFORM_ROUTES to include at least route id and multiple routes, for #95, followup to #47 #103, which can't really work until next DDEV release because the routes.yaml is optional)
• Symfony (https://github.com/symfonycorp/platformsh-symfony-template)
• TYPO3
• Pimcore

[gilzow]

The official template(s) for symfony is here: https://github.com/symfonycorp/platformsh-symfony-template
And then from the branches choose the one you want/need

[gilzow]

I've been told we don't need to worry about Symfony as their cli ships with its own local dev solution. But I need to make sure @lolautruche agrees with this.

[lolautruche]

It is true that Symfony CLI provides an efficient local webserver and good support of Docker for services. Nevertheless, I think we should not neglect it

[gilzow]

for Django template testing:
https://github.com/wsvincent/djangox
https://github.com/django-cms/django-cms
https://github.com/blackfireio/bigfoot-django
https://github.com/mirumee/saleor

[rfay]

The good news is that we already have testing for laravel, which is @chadwcarlson 's highest priority.