Age | Commit message (Collapse) | Author |
|
This replaces the secret_token from rails 4.1 on.
Both are used for securing cookies in the browser. The secret_key_base
will also encrypt the cookies while the token will only sign them.
Keeping the token in there for now allows us to migrate existing sessions
/ cookies to the new secrets. We can remove it in the next version once
all providers have run with secret_key_base for a while.
|
|
We used haproxy because we had multiple bigcouch nodes but now
with a single couchdb node this is not needed anymore.
- Resolves: #8144
|
|
|
|
New soledad packages now depend on Twisted 16.2.0 (see
https://leap.se/code/issues/8412), so we need to pin twisted to get
installed from jessie-backports.
- Resolves: #8418
|
|
|
|
service (Bug #6851)
Also, moved global Exec{} defaults to site.pp
Change-Id: I9ae91b77afde944d2f1312613b9d9030e32239dd
|
|
- Restructure soledad class
- Include soledad::client class on webapp nodes
- Tested: [unstable.bitmask.net]
- Related: #7523
|
|
Done by including a service-dependend site_config::remove::webapp
class.
|
|
|
|
their own files, fix mx logwatch path.
|
|
|
|
|
|
|
|
Change-Id: I8a6c27434f548f24d9dba1a969699200ab307477
|
|
Change-Id: I92f69b6fa30aae953243ae19096e2998810c9ac6
|
|
Change-Id: I56250e05e3a933deacd0b6e02192e712d3fd9fd5
|
|
Conflicts:
platform.rb
puppet/modules/site_config/manifests/hosts.pp
|
|
|
|
|
|
site_mx::haproxy and site_webapp::haproxy only
included site_haproxy. They didn't do anything else.
So just include site_haproxy in manifests/init.pp and
remove the unused classes
|
|
|
|
|
|
Change-Id: Ib2ce0d38a8e4dd30ae6842bfb5579d9c3dd10f18
|
|
Change-Id: Ic1ef7e25f07cbbbcea9bcc90248479009904303e
|
|
for custom git source, improve apache config.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#3838)
|
|
shorewall is setup before the service is setup. This is necessary due to the strict initial firewall that stops various service setup operations from happening, but is relaxed once shorewall is setup properly (#3782)
Change-Id: Ia9640c4118aa0053cdb99e7bc11860fed5527501
|
|
pull things from git (#3756)
Change-Id: If404452c54dedb7a39a910994dc68309257d351d
|
|
Change-Id: Ic700fec9cfb8e8474fb65dbdd4a1a537bf586ec9
|
|
We currently disable the billing gem in production while it's on in development and test. Therefore bundler will not install its dependencies - in particular the braintree gem when deploying.
Since the RAILS_ENV was not specified rake was called with the default of 'development'. It therefore tried to load the development gems and failed when looking for 'braintree'. Specifying the production RAILS_ENV fixes this. It looks like we'll always need to specify RAILS_ENV when calling rake or we might want to export it to the environment in a separate task or the user config files such as .bashrc
|
|
|
|
|
|
|
|
You can either ensure assume-unchanged or ensure those changes are tracked.
Used to keep the git status clean.
|
|
Git normally tracks the dummy files we replace with symlinks. So we tell it to ignore these changes on deploy.
|
|
created beforehand and have the correct permissions.
|
|
'/srv/leap/webapp': }
|
|
|
|
to work with the latest leap_cli.
|
|
|
|
Conflicts:
puppet/modules/site_webapp/manifests/init.pp
Resolved lint differences
Change-Id: Ifbc535ec844222c9f6f0dd71ac12742230bb64ee
|
|
|
|
normally a file resource would automatically require the parent directory first,
but try::file doesn't do this so it has errors if /srv/leap/webapp doesn't exist yet:
for example:
- [web1] err: /Stage[main]/Site_webapp/Try::File[/srv/leap/webapp/public/img]/Exec[restore_/srv/leap/webapp/public/img]/returns: change from notrun to 0 failed: Working directory '/srv/leap/webapp/public' does not exist
that was 'tried' before the vcsrepo was done which would have resolved that
problem. This makes sure that the vcsrepo is done first
|