| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
The app user needs to be able to restart the app because of the current
capistrano setup. The deploy user should not really be the app runner.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- Get bundler and pdftk from raring repo and de-prioritise all other
raring packages
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
| |
Now uses ugly so convert it with the rake task
|
|
|
|
| |
Then re-installers don't have to compile anything.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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 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.
|
| |
|
|
site-specific-install.sh will be called by our generic site
install script in commonlib/bin/install-site.sh
These scripts assume that you have a new installation of
Debian squeeze or Ubuntu precise and then will set up:
- Alaveteli running in development mode with the Thin web
server behing nginx
- The cron jobs that are required for the site to work.
- A basic Postfix configuration for sending and receiving
mail.
We also will use this script for generating new AMIs
(Amazon Machin Images) for Alaveteli.
The general.yml configuration file will be created if it
doesn't exist, but if there is an existing copy it won't be
overwritten, so it should be safe to customize that file and
then re-run the install script.
|