Details
-
Story
-
Resolution: Done
-
High
-
None
-
None
-
None
-
[2.1] Sprint 4
-
1
Description
We have an Enterprise environment for testing on platform.sh.
We want to automatically deploy the eZPEE demo site "Tasteful Planet" on the domain that we own www.tastefulplanet.com upon each stable, to insure tastefulplanet.com runs the latest eZ Platform Enterprise Edition release.
We have not yet defined the policy for the content, we could decide:
- of a nightly reset of the database
- weekly
- upon deployment and then let the content live it's life
- never update (unlikely we want to go this route as each release might come with new demo content)
Attachments
Issue Links
- relates to
-
EZP-28817 The installer installs ezp database in dfs database if dfs cluster is configured
- Open
-
EZP-28819 app/console ezplatform:io:migrate-files won't run if you have dedicated DFS database
- Open
-
EZEE-1869 Having a dedicated database for DFS as recommended does not work
- Open
-
EZEE-1864 Scheduled publishing doesn't work together with Redis cache
- Closed
-
EZEE-1900 Installer fails if auto_increment_increment != 1
- Closed
-
EZP-28800 Make it possible to store session in redis when using platform.sh
- Closed
-
EZP-28816 console cache:clear doesn't remove cache from Redis
- Closed
-
EZP-28814 Make solr work on platform.sh
- Closed
-
EZP-28815 Create helper script which generates solr config
- Open
-
EZEE-1903 Add possibilty to generate solr config which can be used in platform.sh
- Closed