mirror of github.com/vector-im/element-call with some private sauce
Find a file
Dino 6e275b9221
Clarified homeserver requirements
I clarified homeserver requirements (i.e. that Element Call needs a homeserver like Synapse but not necessarily Synapse), and also edited some other parts for clarity. I also updated the recommendation to not log in to an existing homeserver based on my new findings that Element Call *may* allow you to log in to an existing HS but log in is unreliable.
2023-01-26 14:24:53 +00:00
.github Upload source maps to sentry (#810) 2023-01-03 10:48:48 +00:00
.storybook Remove dependency on matrix-react-sdk 2022-04-07 14:22:36 -07:00
.vscode Apply Prettier to the entire project 2022-12-09 14:34:25 -05:00
config Fix caching headers on Docker image 2023-01-12 16:20:37 +00:00
public Translated using Weblate (Japanese) 2023-01-20 17:20:44 +00:00
scripts Simplify build process 2022-12-19 18:43:42 +00:00
src Fix the rageshake modal on mobile 2023-01-23 17:52:02 +00:00
test Merge pull request #783 from robintown/font-params 2022-12-10 18:55:35 -05:00
.dockerignore Add CI 2021-12-20 16:59:39 +00:00
.env.example Make sample config just have the HS config 2022-12-20 18:13:08 +00:00
.eslintrc.cjs Apply Prettier to the entire project 2022-12-09 14:34:25 -05:00
.gitignore Add instructions to put config.json inside public/ 2022-11-09 10:55:21 -05:00
.postcssrc.json Add automatic css prefixing 2021-10-14 17:41:59 -07:00
.prettierignore Add prettier support 2022-05-03 14:24:04 +01:00
.prettierrc.json Add prettier support 2022-05-03 14:24:04 +01:00
babel.config.cjs Add jest 2022-10-26 13:21:06 +02:00
CONTRIBUTING.md Apply Prettier to the entire project 2022-12-09 14:34:25 -05:00
demo.jpg Add a demo screenshot to the README 2023-01-20 10:51:28 -05:00
Dockerfile Upload source maps to sentry (#810) 2023-01-03 10:48:48 +00:00
i18next-parser.config.js Apply Prettier to the entire project 2022-12-09 14:34:25 -05:00
LICENSE Add LICENSE 2021-07-16 14:31:42 -07:00
package.json Use merged js-sdk commit 2023-01-20 13:12:03 +00:00
README.md Clarified homeserver requirements 2023-01-26 14:24:53 +00:00
tsconfig.json Apply Prettier to the entire project 2022-12-09 14:34:25 -05:00
vite.config.js Upload source maps to sentry (#810) 2023-01-03 10:48:48 +00:00
yarn.lock Use merged js-sdk commit 2023-01-20 13:12:03 +00:00

Element Call

Chat Translate

Full mesh group calls powered by Matrix, implementing MatrixRTC.

A demo of Element Call with six people

To try it out, visit our hosted version at call.element.io. You can also find the latest development version continuously deployed to element-call.netlify.app.

Host it yourself

Until prebuilt tarballs are available, you'll need to build Element Call from source. First, clone and install the package:

git clone https://github.com/vector-im/element-call.git
cd element-call
yarn
yarn build

If all went well, you can now find the build output under dist as a series of static files. These can be hosted using any web server of your choice.

You may also wish to add a configuration file (Element Call uses the domain it's hosted on as a Homeserver URL by default, but you can change this in the config file). This goes in public/config.json - you can use the sample as a starting point:

cp config/config.sample.json public/config.json
# edit public/config.json

Because Element Call uses client-side routing, your server must be able to route any requests to non-existing paths back to /index.html. For example, in Nginx you can achieve this with the try_files directive:

server {
    ...
    location / {
        ...
        try_files $uri /$uri /index.html;
    }
}

By default, the app expects you to have a Matrix homeserver (such as Synapse) installed locally and running on port 8008. If you wish to use a homeserver on a different URL or one that is hosted on a different server, you can add a config file as above, and include the homeserver URL that you'd like to use.

Element Call requires a homeserver with registration enabled without any 3pid or token requirements, if you want it to be used by unregistered users. Furthermore, it is not recommended to use it with an existing homeserver where user accounts have joined normal rooms, as it may not be able to handle those yet and it may behave unreliably.

Therefore, to use a self-hosted Synapse homeserver, this is recommended to be a new server where any user account created has not joined any normal rooms anywhere in the Matrix federated network. The homeserver used can be setup to disable federation, so as to prevent spam registrations (if you keep registrations open) and to ensure Element Call continues to work in case any user decides to log in to their Element Call account using the standard Element app and joins normal rooms that Element Call cannot handle.

Development

Element Call is built against matrix-js-sdk. To get started, clone, install, and link the package:

git clone https://github.com/matrix-org/matrix-js-sdk.git
cd matrix-js-sdk
yarn
yarn link

Next, we can set up this project:

git clone https://github.com/vector-im/element-call.git
cd element-call
yarn
yarn link matrix-js-sdk

You're now ready to launch the development server:

yarn dev

Configuration

There are currently two different config files. .env holds variables that are used at build time, while public/config.json holds variables that are used at runtime. Documentation and default values for public/config.json can be found in ConfigOptions.ts.

Translation

If you'd like to help translate Element Call, head over to translate.element.io. You're also encouraged to join the Element Translators space to discuss and coordinate translation efforts.