The current implementation, using the double square bracket [[ for link syntax, is however ignored when renaming cards. If you create a card or plus card and transclude it you can rename it and the transclusions point to the new card. However if you link to it and try to rename it, the links stay the same, and the integrity of what you are trying to build fades away with time.
I've setup this for testing while editing content here on wagn.
See step 6 of Optimizing in the card below. I have included both a link and a transclusion to http://wagn.org/Wagn_on_Apache+public_folder_symlink_prior_to_1_13
If one tries to rename Wagn on Apache+public folder symlink prior to 1.13 to something else, the transclusion still works while the link becomes outdated.
Please note that I'm referring to this syntax [ Wagn on Apache+public folder symlink prior to 1.13 | whatever text one may want to appear in the link ] OR [+public folder symlink prior to 1.13 | whatever text one may want to appear in the link ]. Seems plus cards are supported here also.
To set up Decko behind an Apache webserver, we recommend using Phusion Passenger. In general, you will follow the instructions for deploying a Rack-based Ruby application.
Following the above example, your apache config might look something like this:
<VirtualHost *:80> ... DocumentRoot /srv/mydeck/current/public <Directory /srv/mydeck/current/public> AllowOverride all Options -MultiViews </Directory> </VirtualHost>
You will also need to make sure that the apache user (usually www-data) has read access to config.ru and read/write access to your log, tmp, and file directories
Optimizing
The above should help you get Decko working, but you'll have to do a bit more to make it fast.
- memcache. This is vital for a high-performing deck.
To configure Decko for memcache, add this to your Gemfile:gem 'dalli'
and edit config/application.rb with the following:
config.cache_store = :dalli_store, []
- mod_xsendfile. File and Image cards process permissions before sending the file. This makes that fast.
- mod_expires. Makes use of decko's non-expiring assets so images, stylesheets, and javascript don't slow down page loads at all.
- You'll need to enable mod_headers so that the ht_access will work (Headers directives)