Go to file
2022-09-20 10:30:55 -07:00
.github/workflows Build and push multi-arch Docker images in CI 2022-08-01 16:53:54 +02:00
doc Update the documentation to reference the published docker image 2022-08-01 16:53:54 +02:00
docker Fix the runtime config template to include the default theme 2022-08-01 17:01:25 +02:00
prototypes add prototype to show we can prevent the txn from being aborted on error 2021-09-21 20:58:16 +02:00
scripts v0.0.20 2022-09-16 18:11:41 -07:00
src Merge branch 'bwindels/calls' into thirdroom/dev 2022-09-20 10:30:55 -07:00
.dockerignore chore: optimise Dockerfile 2021-03-14 12:52:35 +01:00
.editorconfig wip 2019-02-17 23:58:01 +01:00
.eslintrc.js fix lint error 2022-05-12 11:53:29 +02:00
.gitignore Ignore macOS metadata .DS_Store (#770) 2022-06-28 05:08:24 -05:00
.gitlab-ci.yml chore: add GitLab CI definition 2021-03-14 13:20:39 +01:00
.ts-eslintrc.js first draft of fully typescriptified LoginViewModel.ts 2022-07-27 22:09:30 -07:00
codestyle.md dont use lookbehind in regular expressions, safari & older firefoxes choke on them 2021-12-08 18:00:37 +01:00
CONTRIBUTING.md remove changelog notes remainder 2022-02-17 17:44:44 +01:00
Dockerfile Make the Docker image configurable at runtime 2022-08-01 16:54:25 +02:00
Dockerfile-dev Required pkg for aarch64 docker build 2021-09-29 19:31:39 -07:00
LICENSE add full license text 2020-08-05 18:40:45 +02:00
package.json Merge branch 'sandhose/oidc-login' into aj-oidc 2022-08-09 12:02:54 +05:30
README.md add notes about client side caching 2022-05-18 19:44:39 +00:00
TODO.md WIP 2020-08-05 18:17:35 +01:00
tsconfig-declaration.json somewhat works, but not everything we need 2021-12-22 16:31:18 +01:00
tsconfig.json Revert back option 2022-07-29 17:33:33 +05:30
view-gallery.html rearrange assets and main.js to make them run with vite 2021-11-08 11:10:23 +01:00
vite.common-config.js Change directory name 2022-07-19 17:56:08 +05:30
vite.config.js Merge branch 'sandhose/oidc-login' into aj-oidc 2022-08-09 12:02:54 +05:30
vite.sdk-assets-config.js Specify theme as array 2022-07-29 23:45:58 +05:30
vite.sdk-lib-config.js Remove unsued imports 2022-04-13 17:44:07 +05:30
yarn.lock Fix merge conflict 2022-08-09 14:23:40 +05:30

Hydrogen

A minimal Matrix chat client, focused on performance, offline functionality, and broad browser support. This is work in progress and not yet ready for primetime. Bug reports are welcome, but please don't file any feature requests or other missing things to be on par with Element Web.

Goals

Hydrogen's goals are:

  • Work well on desktop as well as mobile browsers
  • UI components can be easily used in isolation
  • It is a standalone webapp, but can also be easily embedded into an existing website/webapp to add chat capabilities.
  • Loading (unused) parts of the application after initial page load should be supported

For embedded usage, see the SDK instructions.

If you find this interesting, come and discuss on #hydrogen:matrix.org.

How to use

Hydrogen is deployed to hydrogen.element.io. You can also deploy Hydrogen on your own web server:

  1. Download the latest release package.
  2. Extract the package to the public directory of your web server.
  3. If this is your first deploy:
    1. copy config.sample.json to config.json and if needed, make any modifications (unless you've set up your own sygnal instance, you don't need to change anything in the push section).

    2. Disable caching entirely on the server for:

      • index.html
      • sw.js
      • config.json
      • All theme manifests referenced in the themeManifests of config.json, these files are typically called theme-{name}.json.

      These resources will still be cached client-side by the service worker. Because of this; you'll still need to refresh the app twice before config.json changes are applied.

Set up a dev environment

You can run Hydrogen locally by the following commands in the terminal:

  • yarn install (only the first time)
  • yarn start in the terminal

Now point your browser to http://localhost:3000. If you prefer, you can also use docker.

FAQ

Some frequently asked questions are answered here.