FreakPress is Wordpress fork that is configured to run on the Pantheon platform. This fork is definitely for the developers and is NOT for production use.
NOTE: Pantheon is a Drupal platform and as such no questions regarding Wordpress or Freakpress will be supported. For any bugs or error reports, submit them to the Freakpress issue queue.
Pantheon is development platform optimized and configured to run high performance Drupal sites. There is built-in support for features such as Varnish, redis, Apache Solr, New Relic, Nginx, PHP-FPM, MySQL, PhantomJS and more.
The goal is to keep Freakpress as close to Wordpress as possible and avoid hacking the core. There are four steps to getting a Freakpress install up and running.
Go to the spin-up screen and create your free development site. If you do not have an account, you can create it during the spin-up process.
When the spin-up process is complete, you will be redirected to the site's dashboard. Click on the link under the site's name to access the Dev environment.
How about the Wordpress database config screen? No need to worry about database connection information as that is taken care of in the background. The only step that you need to complete is the site information and the installation process will be complete.
We will post more information about how this works but we recommend developers take a look at wp-congfig.php to get an understanding.
There are a number of plugins can be added to improve the performance and functionality of Freakpress. These have not been fully tested and may require some work to be 100% functional
- W3 Total Cache
- Solr for Wordpress
- wp-shell - (Not available)
There are some breaking changes that should be considered before using Freakpress.
The Pantheon workflow includes three separate environments to work on your site by default - Dev, Test and Live. Through the development process the URLs for the site will change depending on the environment being accessed.
Absolute URLs are standard in Wordpress which can lead to broken links and other quirks. Please be aware of this as some plugins follow this convention so functionality may break as code is moved between environments.
Pantheon is configured for Drupal so the cookie scheme is set to the Drupal convention of the SESS prefix for all cookies. This is handled in wp-config.php by setting configuration variables. For any custom modules that rely on cookies, it will be important to keep this in mind.
If cookies are detected they will be stripped out and this will also prevent Varnish from caching and serving requests.
@TODO
This is an experimental version but if there are any bug reports, or feature enhancements then file a request on the Github issue queue.
@TODO
Fork the repo and create a pull request!