Deploying projects which use ToscaWidgets
Once extracted, comment out the ToscaWidgets alias in your /etc/httpd/conf.d/moksha.conf.
$ orbited -c /etc/moksha/orbited.cfg
By default Moksha utilizes the embeded MorbidQ message broker inside of Orbited. This allows for widgets to communicate with the server using the Stomp protocol. In production you can easily switch to an enterprise-grade message broker, such as Apache Qpid.
See the documentatoin on Message Brokers for how to hook up an AMQP broker.
See also
If you’re interested in using RabbitMQ with Moksha, see the Using RabbitMQ with Moksha docs. Warning: it’s not very well tested or supported, yet.
After installing memcached, you’ll want to update your production.ini configuration to utlize the memcached Beaker extension. This example uses two memcached servers.
beaker.cache.type = ext:memcached
beaker.cache.url = memcached1;memcached2