aboutsummaryrefslogtreecommitdiffstats
path: root/script/rails-post-deploy
Commit message (Collapse)AuthorAgeLines
* Enable rails-post-deploy to be run from any directoryMark Longair2013-04-02-2/+7
| | | | | | | The BASH_SOURCE variable reliably gives the path of the script, so we can make the script work regardless of what the current working directory is on running the script.
* Change email address in header of source code to hello@mysociety.orgMatthew Landauer2013-03-26-1/+1
|
* Even in development, bundle should be installed in the vendor directory. ↵Louise Crow2013-01-15-1/+4
| | | | Fixes #730. Capistrano-based deploys don't use rails-post-deploy, so I don't think this will be a problem for them.
* Don't install the develop or development group of gems in travis.Louise Crow2012-12-17-0/+4
|
* Remove svn tags that are out of date as we are now using gitMatthew Landauer2012-10-09-3/+0
|
* Move the installation of themes to a Rake task so that we can use the ↵Louise Crow2012-08-29-27/+1
| | | | ALAVETELI_VERSION constant to check for tags in themes that indicate compatibility with this version of the Alaveteli codebase.
* Make the post-deploy script actually work, and for both incantations of ↵Seb Bacon2012-07-17-6/+12
| | | | theme installation
* Run optional "post_install" scriptSeb Bacon2012-07-16-0/+6
|
* Revert "Revert "Let’s try fixing bundler instead""Robin Houston2012-05-31-22/+1
| | | | | | | | | This reverts commit 57bfe1f4fd19f766677e08b132d0a16fad2ad706. In fact this time we are not going to try fixing bundler instead, but rather we are going to try to work around the bundler bug in a different way, by uploading our version of xapian-full to rubygems (under a different name: xapian-full-alaveteli).
* Revert "Let’s try fixing bundler instead"Robin Houston2012-05-31-1/+22
| | | | This reverts commit 9f5ad85b6ff541a8e4dc83e91548af9c745d64af.
* Let’s try fixing bundler insteadRobin Houston2012-05-31-22/+1
| | | | Instead of trying to work around the bug in bundler, what if we fixed it?
* local can only be used in a functionRobin Houston2012-05-31-1/+1
|
* Bundler fix for rails-post-deployRobin Houston2012-05-31-8/+30
| | | | | | | | | | | | | Ordinarily we would expect simply to run "bundle install" here. However, at the time of writing there is a bug in bundler that causes gems from github to be rebuilt every time bundle install is run, which makes the process very extremely slow in our case because Xapian takes a long time to build. Running "bundle exec bundle install" is a workaround for this bug. However clearly one cannot run bundle exec till the bundle has initially been installed, so we use a flag file .bundler-has-run to indicate whether we are doing an initial install.
* Correctly iterate over THEME_URLS arraySeb Bacon2012-05-23-2/+3
|
* Introduce ability to install multiple, layered themes.Seb Bacon2012-05-23-0/+10
|
* Use "bundle exec bundle install" (ugh) as a workaround for the fact that in ↵Seb Bacon2012-05-16-2/+2
| | | | deployment mode, the xapian-full gem gets recompiled every time
* Now we use bundler, update all scripts to exec `rake` as `bundle exec rake`Seb Bacon2012-05-04-1/+1
|
* in production mode, ensure we skip development and test gemsSeb Bacon2012-03-13-1/+1
|
* Do 'bundler' stuff in correct orderSeb Bacon2012-03-12-4/+6
|
* cause the post-deploy process to run "bundler install"Seb Bacon2012-02-22-1/+6
|
* Attempt to ensure tests always run using the "test" environment, by:Seb Bacon2012-02-07-14/+13
| | | | | 1) Not overriding any *existing* RAILS_ENV setting in rails_env.rb 2) Always creating a rails_env.rb file
* Create config/rails_env.rb in productionRobin Houston2012-02-06-17/+37
| | | | | | | | | | Partially revert 2eac4bef8d73f47bbe579b6f787ef54b8d782d7a, creating config/rails_env.rb in production only. This should address some of the difficulties with config/rails_env.rb causing unexpected behaviour in development, whilst forcing Rails into production environment where necessary for scripts run from cron etc. Closes #418?
* Get rid of config/rails_env.rbRobin Houston2012-02-02-27/+0
| | | | | | | The rails-post-deploy script was creating a file config/rails_env.rb to force $RAILS_ENV to have the appropriate value. But this is a huge pain during development, and shouldn’t be necessary anyway, so let’s get rid of it.
* don't cause an error if script has been run before (due to trying to create ↵Seb Bacon2011-09-26-2/+5
| | | | existing symlink for downloads)
* Add notes about how to make zipfiles downloadable (and provide for this in ↵Seb Bacon2011-09-15-0/+4
| | | | the rails-post-deply script)
* config/general.yml is just as good as config/generalRobin Houston2011-07-08-1/+1
|
* added option to install a theme from a remote URL as part of ↵Seb Bacon2011-06-14-0/+5
| | | | rails-post-deploy process
* Remove unneeded part of script now symlinks in gitFrancis Irving2009-12-03-4/+0
|
* Probably add Rails itselfFrancis Irving2009-12-03-13/+0
|
* Remove old versions of RailsFrancis Irving2009-12-03-13/+4
|
* Give warning when rails_env.rb is made, as it is very confusing.Francis Irving2009-12-02-0/+15
|
* Changing rspec / rspec_on_rails versionFrancis Irving2009-12-02-4/+4
|
* Oops, put back directory change.Francis Irving2009-10-29-0/+1
|
* Remove making of symlink that isn't usedFrancis Irving2009-10-29-3/+0
|
* shlib in new placeFrancis Irving2009-10-29-1/+1
|
* Now is the application directory, not mysociety CVS dirFrancis Irving2009-10-28-16/+3
|
* With new deploy system, is already in the rails app.Francis Irving2009-10-28-3/+0
|
* Fork of rails-post-deploy in mysociety/bin in CVS.Francis Irving2009-10-28-0/+110
We need it in the same repository, and probably better that it is specific to WDTK anyway.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-21 21:44:38 +0000