aboutsummaryrefslogtreecommitdiffstats
path: root/script
Commit message (Collapse)AuthorAgeLines
* fixup! Have install script use same init script names as manual install docs.Louise Crow2014-08-21-2/+2
|
* fixup! Have install script use same init script names as manual install docs.Louise Crow2014-08-21-1/+1
|
* Have install script use same init script names as manual install docs.Louise Crow2014-08-21-4/+4
|
* Add -y option to install python-software-propertiesGareth Rees2014-08-18-1/+1
|
* Use our own Launchpad Ubuntu repo to get pdftkLouise Crow2014-08-18-6/+11
|
* Precise specific fixesGareth Rees2014-08-18-1/+33
| | | | | - Get bundler and pdftk from raring repo and de-prioritise all other raring packages
* Add script to test vagrant vm provisioningGareth Rees2014-08-13-0/+19
| | | | - e.g. script/test-vagrant-provisioning squeeze64
* Debian specific fixesGareth Rees2014-08-13-0/+22
| | | | | | | - Add wheezy repo to get bundler package which is unavailable in squeeze repo - Get bundler from wheezy repo and de-prioritise all other wheezy packages
* Generate sysvinit with rake taskGareth Rees2014-08-07-4/+7
| | | | Now uses ugly so convert it with the rake task
* Add log/ to switch-to-shared scriptGareth Rees2014-07-10-0/+1
| | | | | | | | script/rails-deploy-before-down will complain if log is listed in the SHARED_DIRECTORIES configuration variable and already exists in APP_ROOT. It will recommend this script be used to migrate to a timestamped deployment structure, so adding log/ makes the transition of the log directory easier.
* Remove mySociety log handling from install scriptsGareth Rees2014-07-10-25/+0
| | | | | | The deployment system should deal with putting logs in the desired place. As this script gets run on a variety of systems it can cause problems for non-mySociety reinstallers.
* Use the run-with-lockfile shell script instead of the C programLouise Crow2014-06-19-1/+0
| | | | Then re-installers don't have to compile anything.
* Rename XXX comments with TODO:Gareth Rees2014-06-10-2/+2
| | | | Picks these up in `rake notes` and adds semantic meaning
* Don't install debug gems for CIGareth Rees2014-05-06-1/+1
|
* Rename develop Gemfile group to debugGareth Rees2014-05-06-1/+1
| | | | Develop is too similar to development to mean anything different.
* Merge branch 'issues/762-travis-before-install' into rails-3-developGareth Rees2014-05-06-3/+4341
|\
| * Use WAD to cache bundles to Amazon S3Gareth Rees2014-05-02-3/+4341
| | | | | | | | https://github.com/Fingertips/WAD
* | Fix formatting of compact-xapian-databaseGareth Rees2014-04-14-14/+17
| |
* | Suppress non-error output compact-xapian-databaseGareth Rees2014-04-14-3/+5
|/ | | | Cron sends an email for all output, whereas generally we only want to get an email if the command exited in error.
* Allow the location of the bundle to be configuredGareth Rees2014-03-11-3/+9
| | | | | | | - Sets vendor/bundle as default - Uses $HOME/bundle when generating general.yml Based on d9f162c8ab08cb881cd68a3eee900c52c63cb1ae
* Merge branch 'hotfix/0.16.0.8' into rails-3-developLouise Crow2014-03-03-1/+2
|\
| * Set the blackhole address as the return path for import error messages.hotfix/0.16.0.8Louise Crow2014-02-28-1/+2
| | | | | | | | | | Also send them directly to the non-bounce address, don't pipe them through mailin again.
* | Merge branch 'feature/batch-requests' into rails-3-developLouise Crow2014-01-29-0/+4
|\ \ | | | | | | | | | | | | | | | Conflicts: config/general.yml-example spec/factories.rb
| * | Send batch requests as a cron job.Louise Crow2013-12-04-0/+4
| | |
* | | Merge branch 'hotfix/0.16.0.6' into rails-3-developLouise Crow2014-01-28-2/+2
|\ \ \ | | |/ | |/|
| * | Set blog and twitter params to empty string0.16.0.6hotfix/0.16.0.6Louise Crow2014-01-28-2/+2
| | | | | | | | | | | | | | | This is the default value from lib/configuration.rb if they aren't set and null values cause errors when .empty? is called on them.
* | | Merge branch 'release/0.16' into rails-3-developLouise Crow2014-01-24-90/+241
|\| |
| * | Add a script to switch mySociety deployments to using shared filesMark Longair2014-01-23-0/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is required by our switch to timestamped-based deploys. There are certain files and directories (e.g. cache, the Xapian databases, generated graphs) that should be shared between deployments, rather than recreating them when creating the next deployment in a new directory. This script should be run as a one-off before switching an instance to using timestamped deploys, to ensure that the existing data is stored in the shared subdirectory of the vhost directory, so that any future deployment can simply create symlinks into the shared directory.
| * | Add the SHARED_FILES_PATH, SHARED_FILES & SHARED_DIRECTORIES optionsMark Longair2014-01-22-0/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | This is to support sharing various files between multiple deployments of Alaveteli. If you have set SHARED_FILES_PATH, SHARED_FILES and SHARED_DIRECTORIES then the rails-deploy-before-down script will ensure that a symlink is created from each of the files or directories mentioned in SHARED_FILES and SHARED_DIRECTORIES to a corresponding path within SHARED_FILES_PATH.
| * | Split rails-post-deploy into rails-deploy-(before|while)-downMark Longair2014-01-22-90/+123
| | |
* | | Rewrite myhostname in /etc/postfix/main.cf in the install scriptMark Longair2013-12-10-0/+5
|/ / | | | | | | | | | | | | This is necessary because the install script is also run on creating a new EC2 instance from the AMI in order to update the configuration with the new internal and external names; the hostname will be different in this case and otherwise myhostname wouldn't be rewritten.
* | Merge branch 'feature/switch-theme-none-option' into rails-3-developMark Longair2013-12-05-8/+17
|\ \ | |/ |/| | | | | Conflicts: script/switch-theme.rb
| * Update the switch-theme.rb script allow switching to no themeMark Longair2013-11-25-8/+17
| |
* | Precompile assets only for production.Louise Crow2013-12-03-1/+4
| | | | | | | | | | Conflicts: script/rails-post-deploy
* | Move themes from vendor/plugins to lib/themesMark Longair2013-12-03-1/+1
| | | | | | | | | | | | | | | | | | | | 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
* | Move acts_as_xapian out of vendor/pluginsMark Longair2013-11-29-1/+1
| | | | | | | | | | This includes making making sure that xapiandbs directory is moved with this version of the code.
* | With Rails 3.2, switching theme requires asset recompilationMark Longair2013-11-29-1/+5
| |
* | Merge branch 'feature/rails-3-2-upgrade-spike' into ↵Mark Longair2013-11-29-0/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | feature/switch-to-asset-pipeline Conflicts: Gemfile.lock app/assets/images/admin-theme/ui-bg_flat_0_aaaaaa_40x100.png app/assets/images/admin-theme/ui-bg_flat_55_fbf9ee_40x100.png app/assets/images/admin-theme/ui-bg_flat_65_ffffff_40x100.png app/assets/images/admin-theme/ui-bg_flat_75_cccccc_40x100.png app/assets/images/admin-theme/ui-bg_flat_75_dadada_40x100.png app/assets/images/admin-theme/ui-bg_flat_75_e6e6e6_40x100.png app/assets/images/admin-theme/ui-bg_flat_75_ffffff_40x100.png app/assets/images/admin-theme/ui-bg_inset-soft_95_fef1ec_1x100.png app/assets/images/admin-theme/ui-icons_222222_256x240.png app/assets/images/admin-theme/ui-icons_2e83ff_256x240.png app/assets/images/admin-theme/ui-icons_454545_256x240.png app/assets/images/admin-theme/ui-icons_888888_256x240.png app/assets/images/admin-theme/ui-icons_cd0a0a_256x240.png app/assets/javascripts/admin.js app/assets/javascripts/admin/jquery-ui.min.js app/assets/javascripts/application.js app/assets/javascripts/jquery-ui.min.js app/assets/javascripts/jquery.flot.errorbars.min.js app/assets/javascripts/jquery.flot.min.js app/assets/javascripts/stats.js app/assets/stylesheets/application.css app/assets/stylesheets/fonts.scss app/views/general/_stylesheet_includes.html.erb app/views/layouts/admin.html.erb app/views/layouts/default.html.erb app/views/public_body/statistics.html.erb config/application.rb config/environments/development.rb
| * | Require activesupport before mail gem.Louise Crow2013-11-12-0/+3
| | | | | | | | | | | | | | | | | | | | | If activesupport isn't present, the mail gem will load it's own version, and when rails is eventually loaded in this script, the warning "warning: already initialized constant VALID CHARACTER" is written to standard error.
* | | Precompile the assets in rails-post-deployMark Longair2013-11-26-0/+2
| |/ |/|
* | Merge branch 'install-script' into rails-3-developMark Longair2013-11-07-43/+354
|\ \
| * | Set 'constraint_disabling: false' for tests in database.ymlMark Longair2013-11-07-0/+1
| | | | | | | | | | | | | | | Without this setting, the PostgreSQL user still has to be a superuser for the tests to work without constraint disabling errors.
| * | Rename /etc/postfix/regexp to /etc/postfix/transportsMark Longair2013-11-07-8/+7
| | | | | | | | | | | | | | | | | | | | | | | | This seems slightly less confusing, since both this file and /etc/postfix/recipients contain regexp patterns. This also switches to replacing any transport_maps file that was in use and overwrites the existing file rather than modifying it.
| * | Reduce "backscatter" bounce risk by setting local_recipient_mapsMark Longair2013-11-07-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Leaving the local_recipient_maps setting empty has a risk which is described in the Postfix manual: "[...] That is, an empty value. With this setting, the Postfix SMTP server will not reject mail with "User unknown in local recipient table". Don't do this on systems that receive mail directly from the Internet. With today's worms and viruses, Postfix will become a backscatter source: it accepts mail for non-existent recipients and then tries to return that mail as "undeliverable" to the often forged sender address." This commit changes the local_recipient_maps setting to only accept (and potentially bounce) emails where the local part is known (one that we've mentioned in general.yml) or to a Unix user that exists. Fixes #1166
| * | Invoke commands as the unprivileged user in a login shellMark Longair2013-11-07-3/+3
| | | | | | | | | | | | | | | | | | | | | On some setups, the unprivileged user's .bashrc file won't be sourced unless you've started a login shell - we need that to be sourced to add the gem's bin directory to the PATH, or "bundle" won't be found, for example.
| * | Remove make-crontab and update INSTALL.mdMark Longair2013-11-07-16/+0
| | | | | | | | | | | | | | | | | | The make-crontab script is now redundant, so instead direct people to use the config_files:convert_crontab rake task for generating a crontab file.
| * | Add a rake task to rewrite the crontab-example fileMark Longair2013-11-07-4/+5
| | | | | | | | | | | | | | | | | | 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.
| * | Switch to using 'rake config_files:convert_init_script'Mark Longair2013-11-07-6/+3
| | | | | | | | | | | | | | | | | | Rather than reimplement the processing of the ugly file with sed, we can use the existing rake task for rewriting config/alert-tracks-debian.ugly.
| * | If the origin/install-script branch exists, use that in preferenceMark Longair2013-11-07-7/+4
| | | | | | | | | | | | | | | | | | Once merged to master we can remove origin/install-script, but development is awkward without it. This commit also makes it easy to have an arbitrary number of fallbacks.
| * | We don't use foi-purge-varnish ourselves, so remove itMark Longair2013-10-31-7/+1
| | | | | | | | | | | | | | | | | | We had various problems with the foi-purge-varnish script ourselves that led to us removing it, so it seems like a bad idea to be implicitly suggesting that others should use it.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-27 01:35:04 +0000