| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
| |
This is important under ruby 1.9 in order to determine the
encoding that will be used for new strings created in the code in
the file.
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
script/switch-theme.rb
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These are essentially required in exactly the same way as before, but
from lib/themes rather than vendor/plugins. This is the simplest
possible change in order make the themes work outside vendor/plugins,
I think, but it's not necessarily ideal. It would be worth considering
whether these should be changed to Rails engines, as described here:
http://guides.rubyonrails.org/engines.html
|
| |/ |
|
|
|
When working locally, it's useful to be able to switch between
themes quickly, which essentially involves:
- Updating the general.yml symlink to point to a theme-specific one
- Updating the public/alavetelitheme symlink
- Making sure that the theme exists as vendor/plugins/<theme-name>
This script lets you switch between themes kept in a directory
which is by default called 'alaveteli-themes' at the same level
as your Alaveteli git repository, or can be overriden by the
environment variable ALAVETELI_THEMES_DIR.
|
