You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Florian Keller 7a05d34a21
chore(deps): Upgrade webapp-module-bubble from 1.1.1 to 1.1.2 (#6975)
2 days ago
.elasticbeanstalk chore: Release production version via master tag (#6854) 1 week ago
.github feat: Add a no-response bot (#2976) 7 months ago
.idea feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) 6 months ago
app-config chore: Release production version via master tag (#6854) 1 week ago
bin chore(deps-dev): bump @wireapp/prettier-config from 0.2.0 to 0.3.0 (#6848) 2 weeks ago
docs docs: Add screenshot for staging bump (#6594) 2 months ago
grunt/config refactor: Remove unused vars from args (#5892) 4 months ago
server chore(deps): [security] bump lodash from 4.17.11 to 4.17.14 in /server (#6933) 1 week ago
src runfix: Deactivate legal hold system messages (#6943) 1 week ago
test runfix: Don't override legal hold state for outgoing messages (#6931) 1 week ago
.copyconfigrc.js chore: Release production version via master tag (#6854) 1 week ago
.editorconfig Initial commit 3 years ago
.env.localhost test: Enable debugging by default on localhost (#6946) 6 days ago
.eslintignore feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) 6 months ago
.eslintrc.json chore: Apply ESLint and Prettier config (#6376) 3 months ago
.gitattributes Initial commit 3 years ago
.gitignore refactor: Use nyc to check types (#6025) 4 months ago
.huskyrc.js refactor: Modularize events (part 1) (#6452) 2 months ago
.npmrc chore: Use npm registry (#4069) 1 year ago
.stylelintrc.json feat: Add stylelint mostly for consistent ordering (#2968) 1 year ago
.travis.yml runfix: Deploy edge branch to edge environment (#6944) 6 days ago
Dockerfile runfix: Docker copy env.defaults file (#6604) 2 months ago
Gruntfile.js feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) 6 months ago
LICENSE Initial commit 3 years ago
README.md chore: Release production version via master tag (#6854) 1 week ago
babel.config.js chore: Enable lazy loading of bundles (#6770) 3 weeks ago
crowdin.yaml refactor: Combine logged-out & logged-in translations (#5777) 5 months ago
i18next-scanner.config.js refactor: Combine logged-out & logged-in translations (#5777) 5 months ago
karma.conf.js chore: Enable the --specs flag for *.test.ts files (#6809) 3 weeks ago
karma.conf.react.js chore: Add the nolegacy option to run tests faster (#5847) 4 months ago
locations.js feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) 6 months ago
package.json chore(deps): Upgrade webapp-module-bubble from 1.1.1 to 1.1.2 (#6975) 2 days ago
postcss.config.js chore: Happy new year (#2467) 1 year ago
run.sh chore: Build Docker images (#6533) 2 months ago
tsconfig.json refactor: Rename path aliases (#6479) 2 months ago
tslint.json chore: Remove console output (#6579) 2 months ago
tslint.react.json chore: Different linting rules for React (#6790) 3 weeks ago
webpack.config.common.js chore: Enable lazy loading of bundles (#6770) 3 weeks ago
webpack.config.dev.js feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) 6 months ago
webpack.config.js refactor: Rename path aliases (#6479) 2 months ago
webpack.config.test.js refactor: Rename path aliases (#6479) 2 months ago
yarn.lock chore(deps): Upgrade webapp-module-bubble from 1.1.1 to 1.1.2 (#6975) 2 days ago

README.md

Wire™

We are hiring

This repository is part of the source code of Wire. You can find more information at wire.com or by contacting opensource@wire.com.

You can find the published source code at github.com/wireapp/wire.

For licensing information, see the attached LICENSE file and the list of third-party licenses at wire.com/legal/licenses/.

If you compile the open source software that we make available from time to time to develop your own mobile, desktop or web application, and cause that application to connect to our servers for any purposes, we refer to that resulting application as an “Open Source App”. All Open Source Apps are subject to, and may only be used and/or commercialized in accordance with, the Terms of Use applicable to the Wire Application, which can be found at https://wire.com/legal/#terms. Additionally, if you choose to build an Open Source App, certain restrictions apply, as follows:

a. You agree not to change the way the Open Source App connects and interacts with our servers; b. You agree not to weaken any of the security features of the Open Source App; c. You agree not to use our servers to store data for purposes other than the intended and original functionality of the Open Source App; d. You acknowledge that you are solely responsible for any and all updates to your Open Source App.

For clarity, if you compile the open source software that we make available from time to time to develop your own mobile, desktop or web application, and do not cause that application to connect to our servers for any purposes, then that application will not be deemed an Open Source App and the foregoing will not apply to that application.

No license is granted to the Wire trademark and its associated logos, all of which will continue to be owned exclusively by Wire Swiss GmbH. Any use of the Wire trademark and/or its associated logos is expressly prohibited without the express prior written consent of Wire Swiss GmbH.

How to build the open source client

Build

Installation

  1. Install Node.js
  2. Install Yarn: npm install -g yarn
  3. Run yarn
  4. Rename .env.localhost to .env in order to run the app in a local environment

Execution

Run yarn start and Wire’s web app will be available at: http://localhost:8080/auth/#login

To login with your existing Wire account use: http://localhost:8080/auth/?env=prod#login

Testing

To launch the full test suite (types check + linting + server tests + app tests), simply run

yarn test

Alternatively, you can run specific parts of the app:

yarn test:(server|types|auth|app)

Since the test suite for the app is the biggest test suite, you might want to run a single test file, in which case, you can use the --specs option:

yarn test:app --specs spec1[,spec2...]

where specN is the path to the spec to run relative to test/unit_tests and without Spec.js.

Speed up testing for files fully migrated to the module system

When a file (and all its dependencies) do not rely on any global dependency, then you can use the --nolegacy flag to run the tests on that single file.

yarn test:app --specs spec1 --nolegacy

The test should start very quickly (webpack won’t have to resolve all the global dependencies).

If the test doesn’t run with the nolegacy option (but runs without), it means it’s depending, somehow, on, at least, one thing that should be on the global scope.

Example

If you want to run the tests for the ConversationRepository, the file containing the test is:

test/unit_tests/conversation/ConversationRepositorySpec.js

The command to run is:

yarn test:app --specs conversation/ConversationRepository

Deployment

General workflow

Stage Branch Action Environment Backend
1 edge commit wire-webapp-edge Staging
2 dev commit wire-webapp-dev Staging
3 dev tag (format: YYYY-MM-DD-staging.X) wire-webapp-staging Production
4 master commit wire-webapp-master Staging
5 master tag (format: YYYY-MM-DD-production.X) wire-webapp-prod Production

Before RC testing we create a merge commit from “dev” to “master” branch, so that our QA team can run tests on the latest version of our app.

Staging Bumps

Actions

  1. Checkout commit ID which has been approved by QA team
  2. Create a Git tag with the following format: YYYY-MM-DD-staging.X
  3. Push the newly created tag

Example

git checkout 90fda951916f0d60a5bffce69a7267830e313391
git tag 2019-04-23-staging.0
git push origin --tags

If everything is done right, you will see a Travis CI job in the build pipeline based on the new tag:

Staging Release

Production Release

Similar to “Staging Bumps” with the exception that tags are made from “master” branch and contain “production” in the tag name instead of “staging”. Example: 2019-07-01-production.0

Manual Deployments

Based on the Git branch, builds get deployed automatically by Travis CI. In case Travis CI is not working, a manual deployment can be triggered using yarn deploy.

A manual deployment requires the local setup of the Elastic Beanstalk Command Line Interface (EB CLI). Manual deployments are also based on branch defaults which are configured here.

Status

Build Status styled with prettier

Translations

All Wire translations are crowdsourced via Crowdin.