| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
Install script on AWS uses development mode by default
|
| |
|
| |
|
|
|
|
|
| |
ENV[‘SITE’] can be specified for the crontab (and elsewhere) so
allow the option here too.
|
|
|
|
|
| |
Deployment system should handle linking the original location to
wherever necessary on the specific platform.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Less manual editing for reinstallers.
Existing backwards-compatibility:
$ bundle exec rake config_files:convert_crontab \
DEPLOY_USER=deploy \
VHOST_DIR=/home/vagrant/ \
VCSPATH=alaveteli \
SITE=alaveteli \
CRONTAB=config/crontab-example | grep 'MAILTO='
MAILTO=cron-alaveteli@mysociety.org
New optional MAILTO option:
$ bundle exec rake config_files:convert_crontab \
DEPLOY_USER=deploy \
VHOST_DIR=/home/vagrant/ \
VCSPATH=alaveteli \
SITE=alaveteli
CRONTAB=config/crontab-example \
MAILTO=cron@example.org | grep 'MAILTO='
MAILTO=cron@example.org
|
|
|
|
|
|
| |
As suggested by Louise Crow, this new rake task reuses
the convert_ugly function to rewrite the crontab-example
file into a usable crontab file.
|
|
|
|
|
| |
I assume 'skip' must have been an argument to this function
before it was introduced into our repository.
|
| |
|
|
replacement and uncomments the RAILS_ENV setting and exporting (substituting in the current RAILS_ENV) if there's no config/rails_env.rb
|