bc2e7a7366
So far, the Dockerfile built hydrogen on the server running the image, instead of building it during the building of the image. This blew up the image size immensely and caused node+yarn to run in the resulting image. This new Dockerfile builds hydrogen in a separate build stage and then moves the target directory into an nginx based container image, which takes care of serving the target webroot. The existing Dockerfile has been moved to Dockerfile-dev for usage as a development environment. The docs have been adjusted accordingly. Additionally, this switched from a fixed alpine version of the node image to the latest alpine version, and changed the container image references in the `FROM` statements to use the fully qualified references including the registry domain. |
||
|---|---|---|
| assets | ||
| doc | ||
| prototypes | ||
| scripts | ||
| src | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitignore | ||
| Dockerfile | ||
| Dockerfile-dev | ||
| LICENSE | ||
| README.md | ||
| TODO.md | ||
| codestyle.md | ||
| index.html | ||
| package.json | ||
| yarn.lock | ||
README.md
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
If you find this interesting, come and discuss on #hydrogen:matrix.org.
How to use
Hydrogen is deployed to hydrogen.element.io. You can run it locally yarn install (only the first time) and yarn start in the terminal, and point your browser to http://localhost:3000. If you prefer, you can also use docker.
FAQ
Some frequently asked questions are answered here.