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/.
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
- Install Node.js
- Install Yarn
.envin order to run the app in a local environment
- Use a browser with disabled web security (
−−disable−web−securityin Chrome) to circumvent CORS issues when connecting to our backend from localhost
yarn start and Wire's web app will be available at: https://localhost:8081/auth/
To launch the full test suite (types check + linting + server tests + app tests), simply run:
Alternatively, you can test specific parts of the app:
Bypass Chrome's security restrictions for local development:
- Add the following entry to your hosts file:
- Restart your Chrome browser with flags:
--disable-web-security --ignore-certificate-errors --user-data-dir=...
Host file location:
- On macOS / Linux the hosts file can be found at:
- On Windows 10 the hosts file can be found at:
Optional: If your browser does not trust the certificate from "local.zinfra.io":
- Download mkcert
CAROOTenv variable to
|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
- Get commit ID which has been approved by QA team
yarn release:staging <commitId>(if the commit ID is omitted, the latest commit from
devwill be used).
yarn release:staging 90fda951916f0d60a5bffce69a7267830e313391
- Enter "yes"
If everything is done right, you will see a Travis CI job in the build pipeline based on the new tag:
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.
Similar to "Staging Bumps" with the exception that you need to run
yarn release:production <commitId> (if the commit ID is omitted, the latest commit from
master will be used).
yarn release:production 90fda951916f0d60a5bffce69a7267830e313391
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.
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
All Wire translations are crowdsourced via Crowdin.
Add new strings
- Install Crowdin CLI v3
- Verify you have a
keys/crowdin.yamlin place with the project's API Key and your personal access token (you may have to create one).
- Add string variable and text to "i18n/en-US.json"
- Verify your string shows up on Crowdin project: wire-webapp
- Add translation on Crowdin
- Approve translation on Crowdin
Template of "keys/crowdin.yaml" (you need to create this file yourself):
api_token: your-personal-access-token-from-crowdin api_key: wire-webapp-api-key-from-crowdin
Contributions are welcome! Feel free to check our issues page.
The following commits will help you getting started quickly with our code base: