Skip to content
👽 Wire for web
JavaScript TypeScript HTML CSS
Branch: dev
Clone or download
lipis refactor: Migrate CopyToClipboard to TypeScript (#7543)
* refactor: Migrate CopyToClipboard to TypeScript

* public
Latest commit e4104bc Oct 23, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.elasticbeanstalk
.github feat: Add a no-response bot (#2976) Nov 29, 2018
.idea feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) Jan 10, 2019
app-config chore: Update app config to 0.24.12 (#7412) Oct 11, 2019
bin
docs
grunt/config feat: Turn invite bubble into modal (#7544) Oct 23, 2019
server feat: Turn invite bubble into modal (#7544) Oct 23, 2019
src refactor: Migrate CopyToClipboard to TypeScript (#7543) Oct 23, 2019
test feat: Turn invite bubble into modal (#7544) Oct 23, 2019
.copyconfigrc.js refactor: Remove unused import from copy config (#7262) Sep 9, 2019
.editorconfig Initial commit Jul 21, 2016
.env.localhost test: Enable debugging by default on localhost (#6946) Jul 11, 2019
.eslintignore
.eslintrc.json chore: Apply ESLint and Prettier config (#6376) Apr 17, 2019
.gitattributes Initial commit Jul 21, 2016
.gitignore feat: App lock (#7187) Aug 26, 2019
.huskyrc.js refactor: Modularize events (part 1) (#6452) Apr 24, 2019
.npmrc chore: Use npm registry (#4069) Jul 17, 2018
.stylelintrc.json feat: Add stylelint mostly for consistent ordering (#2968) Mar 28, 2018
.travis.yml chore: AVS environment deployment (#7541) Oct 23, 2019
Dockerfile runfix: Docker copy env.defaults file (#6604) May 15, 2019
Gruntfile.js feat: Turn invite bubble into modal (#7544) Oct 23, 2019
LICENSE Initial commit Jul 21, 2016
README.md
babel.config.js
changelog.js chore: Automate changelog generation (#7332) Sep 24, 2019
crowdin.yaml refactor: Combine logged-out & logged-in translations (#5777) Feb 12, 2019
i18next-scanner.config.js refactor: Combine logged-out & logged-in translations (#5777) Feb 12, 2019
karma.conf.js feat: Add the single value store (#7125) Aug 19, 2019
karma.conf.react.js
locations.js feat: Make logos, icons & audio files customizable (WEBAPP-5685) (#5576) Jan 10, 2019
package.json feat: Turn invite bubble into modal (#7544) Oct 23, 2019
postcss.config.js chore: Happy new year (#2467) Feb 14, 2018
run.sh chore: Build Docker images (#6533) May 6, 2019
tsconfig.json refactor: Rename path aliases (#6479) Apr 26, 2019
tslint.json feat: Turn invite bubble into modal (#7544) Oct 23, 2019
tslint.react.json feat: Turn invite bubble into modal (#7544) Oct 23, 2019
webpack.config.common.js chore: Turn util.js into TS Sep 18, 2019
webpack.config.dev.js chore: Add react-dom hot-loader to use React 16.6+ features (#7119) Aug 19, 2019
webpack.config.js refactor: Integrate AVS API (#6308) Aug 19, 2019
webpack.config.test.js refactor: Rename path aliases (#6479) Apr 26, 2019
yarn.lock feat: Turn invite bubble into modal (#7544) Oct 23, 2019

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) does not rely on any global dependency (i.e. window.z.util), 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 on at least one dependency from the global window namespace.

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 (Feature development) edge commit wire-webapp-edge Staging
2 (Nightly test automation) dev commit or squash merge from edge wire-webapp-dev Staging
3 (Internal release) dev tag (format: YYYY-MM-DD-staging.X) wire-webapp-staging Production
4 (RC testing) master merge (don't squash) from "dev"; afterwards generate release notes wire-webapp-master Staging
5 (Production release) master tag (format: YYYY-MM-DD-production.X) wire-webapp-prod Production

Staging Bumps for internal releases

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

RC testing

Before RC testing we create a merge commit (don't squash!) from "dev" to "master" branch, so that our QA team can run tests on the latest version of our app.

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

Release notes

Release notes need to be generated with yarn changelog after merging to "master" and before creating the new production release tag. Release notes will be locally available (not committed to the repository) in ./CHANGELOG.md and sent to our marketing team to create release notes on Medium.

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.

You can’t perform that action at this time.