Age | Commit message (Collapse) | Author |
|
If a soledad sync test script is already running, there's no need to run
another one. This avoids having multiple test script hanging and eating
up resources.
We have seen this situation under development circumstances, when the
soledad server has been modified in a way that the client hangs and
never finishes.
|
|
If for any reason a sync takes too long, the script will timeout and log
an errro.
|
|
|
|
Switching to using 'master' for development, the 'develop' branch will
no longer receive commits, so we are merging what is in 'develop' into
master.
|
|
|
|
Sometimes nickserver is listed with `ruby /usr/bin/nickserver start`
in the process table, sometimes with `/usr/bin/ruby /usr/bin/nickserver start`.
We should do proper checking with `systemctl status nickserver` to make
sure the service is up though (https://leap.se/code/issues/8579).
Meanwhile it's ok to not do strict checking.
|
|
|
|
|
|
|
|
|
|
https://0xacab.org/leap/leap_se/blob/master/docs/README.md process
|
|
|
|
The develop branch was removed, and current master is the same as
develop was before.
|
|
This HTTP response header enables the Cross-site scripting (XSS) filter
built into some modern web browsers. This header is usually enabled by
default anyway, so the role of this header is to re-enable the filter
if it was disabled maliciously, or by accident.
|
|
Setting this header will prevent the browser from interpreting files as
something else than declared by the content type in the HTTP
headers. This will prevent the browser from MIME-sniffing a response
away from the declared content-type.
When this is not set, older versions of Internet Explorer and Chrome
perform MIME-sniffing on the response body, potentially causing the
response body to be interpreted and displayed as a content type other
than the declared content type.
|
|
|
|
|
|
|
|
upgrade: nickserver version 0.9.x
See merge request !49
|
|
|
|
When the soledad couch user is not present, soledad-server
refuses to start, so we need to ensure that couch is setup correctly
before starting soledad-server.
see https://leap.se/code/issues/8535
|
|
|
|
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
|
|
|
|
|
|
|
|
when using gitlab-runner locally, CI_BUILD_ID is always 1 which
will conflict with running/terminating AWS instances in subsequent runs
therefore we pick a random number in this case
|
|
|
|
- Assemble cloud.json from aws credential env vars
- Deploy ssh private key from env var
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Starting with a recent debian stable point release update, it is
possible that the system is in an inconsistent library state. For
example, puppet could not be run because the libraries on the system
were not the ones that the puppet package was built against. So that
means that deploys could not happen until we've dont a dist-upgrade.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
is configured
The problem is that we have a single onion address per server, so if more
than one domain is configured we need to make sure they don't both try to
use the same onion address.
|
|
|