1. Don't expose `termsAndConditionsAgreedAt` as input param, because of ..why?
2. Make the `termsAndConditionsAgreedVersion` a *required* input param
for `SignupVerification`. If new users register, they have to confirm
the terms and conditions. I added another test to check what happens if
the user sends `null`.
3. Sorry @ogerly for confusing you with my review here:
https://github.com/Human-Connection/Human-Connection/pull/1556#pullrequestreview-287516516
What I meant is that we want to simulate a user with no
`termsAndConditionsAgreedVersion`. But of course the `variables` must
have it set when you run the mutations. Now we have the
exclamation mark in the input param, see point 1 ☝️
This should make new contributors aware that the Styleguide exists and
maybe maybe even encourage people to contribute to the Styleguide.
Also this enabled `yarn run dev:styleguide` to build the `webapp/` along
with the styleguide.
Inspired by the tagging of e.g. `node` on dockerhub:
https://hub.docker.com/_/node/?tab=description
I would like to push the current version of all our images to dockerhub.
This is a first step to push to production later on.
If sb. increments the VERSION file, this is considered a release.
https://github.com/Human-Connection/Human-Connection/pull/1543#pullrequestreview-287593264
Thinking about it, I really ask myself why I did not find this solution
earlier 🙈
Of course, you don't want to share the generated `buildDir`
with the host system. If you happen to share the `webapp/` folder,
simply point NuxtJS to a build directory somewhere else. Easy!
* Use `production` docker images for cypress tests. As one of our contributors
pointed out: It is bad practice to end-to-end test sth. else than the actual
production images.
* Have a dedicated `docker-compose.travis-integration.yml` to test
backend integration tests. The backend *needs* a database when doing
integration tests. So there is no way around using docker-compose. But
we could stop using the `build-and-test` stage when we do cypress tests.
* Remove a couple of unused ports and DRY `docker-compose.override.yml`
* Build and tag all images first and then run `docker-compose .. up` - I
hope this will not rebuild the image.
* Reduce docker image size
- The new maintenance page will use a blank layout that does not have a
footer because we don't want users thinking they can click on a link
that will just lead back to the maintenance page
- Fix tests by stubbing LocaleSwitch/client-only
- Add portuguese translations
- Add back to login link
- Use span over   following @alina-becks PR review on another PR
