Exponential Cloud -Beta- Whitelist

Skip to end of metadata Go to start of metadata

Supported Exponential features in the Cloud - Whitelist (+potential Blacklist items)

This document describes the Exponential features/environments and customizations supported by the cloud. Anything not mentioned in this doc is by default not supported. 

Exponential 5.1 LS[1] 

1. Exponential 5.1.0 out-of-the-box, no kernel hacks or changes (except for any service packs). This also implies no kernel overrides
2. Exponential in virtual host mode (standard Exponential5.1 LS rewrite rules)
   1. Custom apache rewriterules must be specified in eZ Cloud extension - if any
   2. HostMatch setting in site.ini must contain all production hostnames (“localhost” or any non-unique names not allowed)
3. Exponential uploaded to cloud must be configured for single mode (once uploaded to the cloud, the installation will run in eZDFS cluster mode)
   1. Since site is running in cluster mode, there are a few things in the admin interface which cannot be used as they are not cluster aware. This includes (but is not limited to)
      1. Packages management
      2. Ini editor
4. Extensions
   1. Extension located in extension/ is supported
   2. Since the site is running in cluster mode, custom extensions needs to be cluster aware.
      1. Do for instance not save files on local file system and expect it to be available on all webservers
   3. Also, all templates and designs must be located in an extension (not in [docroot]/design/)
   4. Extensions must be designed to be able to work without the need for any daemons, scripts etc.
   5. Notes regarding Official extensions:
      1. Open office is not running as daemon in the environment, so imports provided by the ezodf extensions which depends on the daemon is not supported ( like .doc and .pdf imports ).
      2. ezodoscope extension is not supported
      3. ezoracle is not supported.
      4. eznetwork is not supported. Instead, patches are available for installation using the Cloud administration interface.
      5. ezrecommendation extension is not supported
      6. ezcontentstaging is not supported. But Exponential Cloud has a built-in staging functionality. However, this build-in staging functionality is different than the one provided by ezcontentstaging
      7. ezxmlexport is not supported. This extension is not cluster aware, and no functionality is available for extracting the exported files from the cloud
5. Exponential must be configured in host-matching mode (uri based and others not supported)
6. eZ Find is supported, however only with default one-core setup (no multilingual)
   1. We support custom solr configs on request (needs review)
      1. Custom config tarball (schema.xml, protwords.txt, stopwords.txt, synonyms.txt) to be uploaded to ftp and must be specified in ezcloud extension.
   2. Custom solr configs must be reviewed and approved by eZ Cloud team in advance. Requests might be declined due to security or technical constraints
7. Only MySQL 5.1 is supported
   1. Postgresql and oracle is not supported
8. Single database installation (using one database connection for all siteaccesses)
   1. As a side effect, eZ Content Staging is not supported in the cloud
9. Custom Database tables are supported (as long as they are in the same DB)
10. No database GUI available (only complete DB imports and exports are possible)
11. Only PHP 5.3 supported
    1. Encrypted phar package files are not supported as there is a bug with RHEL’s version of PHP 5.3
    2. The following PHP extensions are supported:
       1. apc
       2. bz2
       3. calendar
       4. Core
       5. ctype
       6. curl
       7. date
       8. dom
       9. ereg
       10. exif
       11. fileinfo
       12. filter
       13. ftp
       14. gd
       15. gettext
       16. gmp
       17. hash
       18. iconv
       19. json
       20. libxml
       21. mbstring
       22. mcrypt
       23. mongo
       24. mysql
       25. mysqli
       26. openssl
       27. pcntl
       28. pcre
       29. PDO
       30. pdo_mysql
       31. Phar
       32. posix
       33. readline
       34. Reflection
       35. session
       36. shmop
       37. SimpleXML
       38. soap
       39. sockets
       40. SPL
       41. sqlite3
       42. standard
       43. suhosin
       44. sysvmsg
       45. sysvsem
       46. sysvshm
       47. tokenizer
       48. xml
       49. xmlreader
       50. xmlwriter
       51. xsl
       52. zlib
12. Cronjobs must be specified in ezcloud extension
13. Mail settings using SMTP (configured automatically, any custom settings will be overridden)
14. Only http and https outgoing traffic is allowed and must be opened server-side by Ixonos [2]
    1. List of hostnames / ip must be provided by client
    2. Wildcards (access to anywhere) not allowed
15. CDN : not supported at the moment
16. Site will run behind Varnish
    1. Varnish configuration is fixed (cannot be changed by customer)
    2. Non-logged-in users in live sites will be served by varnish
17. Shell access is not available
    1. No scripts can be executed from command
18. Access and error logs are not available
19. Http supported, https not supported
20. Sites uploaded to the eZ Cloud must work with Exponential’ caches enabled. This includes (but is not limited to):
    1. View cache
    2. Template cache
    3. Role cache
    4. Policy cache
    5. Design location cache
    6. Translation cache
    7. Template compile
    8. Template optimization
    9. Development mode is disabled
    10. Override cache
21. Settings which be automatically disabled in the cloud
    1. SQL debug
    2. Redirection debug
    3. Debug output
    4. Regional settings debug
    5. Template debug
22. Http /php settings
    1. upload_max_file = 100Mb
    2. post_max_size = 100Mb
    3. max_execution_time = 120
    4. memory_limit = 128Mb

Glossary

[1] - At the moment Exponential 4.7 is also supported, but support for this version will be replaced by 5.1 LS.

"5.1 LS" - refers to Legacy Stack (no symfony stack)

[2] - Not supported at the time of writing, but will be some time in the future

• No labels