gaja-group
/
element-web
forked from matrix/element-web
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Matrix Referenz Client (Web Version)
663 Commits 964 Branches 0 Tags 74 MiB
HTML 37.5%
JavaScript 26.2%
TypeScript 21.9%
Python 6%
Shell 4.6%
Other 3.8%
Go to file
Matthew Hodgson 5844fb4020 spell out that developers need to use npm link 2015-10-25 11:56:29 +00:00
docs Actually add the doc 2015-09-17 11:06:50 +01:00
src s/getMembersWithMemership/getMembersWithMembership/ 2015-10-25 11:51:17 +00:00
vector oops - wrong branch 2015-10-23 02:38:32 +01:00
.gitignore oops - wrong branch 2015-10-23 02:38:32 +01:00
.npmignore Tweak the example build process. Move example -> examples/trivial to we can have more than one. Update README appropriately. 2015-07-03 15:56:04 +01:00
AUTHORS.rst changelog, authors and contributing files 2015-08-10 18:09:35 +01:00
CHANGES.rst Call initial release 0.1.0 and this release 0.1.1 2015-08-10 18:19:30 +01:00
CONTRIBUTING.rst changelog, authors and contributing files 2015-08-10 18:09:35 +01:00
LICENSE Basic structure of a react SDK and start of an implementation. 2015-06-09 17:40:42 +01:00
README.md spell out that developers need to use npm link 2015-10-25 11:56:29 +00:00
config.json Add config file for default hs/is urls 2015-10-02 11:48:52 +01:00
package.json Use new js-sdk modified time to avoid unnecessary member tile updates. Also avoid double-updating since we were setting state and then forcing an update which is redundant. 2015-10-13 11:10:43 +01:00
webpack.config.js Relative-ize paths in webpack config: they're supposed to be relative but sometimes they aren't. 2015-10-23 10:16:00 +01:00

README.md

Vector/Web

Vector is a Matrix web client built using the Matrix React SDK (https://github.com/matrix-org/matrix-react-sdk).

Getting started

  1. Install or update node.js so that your npm is at least at version 2.0.0
  2. Clone the repo: git clone https://github.com/vector-im/vector-web.git
  3. Switch to the SDK directory: cd vector-web
  4. Install the prerequisites: npm install
  5. Start the development builder and a testing server: npm start
  6. Wait a few seconds for the initial build to finish.
  7. Open http://127.0.0.1:8080/ in your browser to see your newly built Vector.

With npm start, any changes you make to the source files will cause a rebuild so your changes will show up when you refresh.

For production use, run npm run build to build all the necessary files into the vector directory and run your own server.

Development

For simple tweaks, you can work on any of the source files within Vector with the setup above, and your changes will cause an instant rebuild.

However, all serious development on Vector happens on the develop branch. This typically depends on the develop snapshot versions of matrix-react-sdk and matrix-js-sdk too, which isn't expressed in Vector's package.json. To do this, check out the develop branches of these libraries and then use npm link to tell Vector about them:

  1. Link the react sdk package into the example: npm link path/to/your/react/sdk
  2. Start the development rebuilder in your react SDK directory: npm start

Similarly, you may need to npm link path/to/your/js/sdk in your matrix-react-sdk directory.

If you add or remove any components from the Vector skin, you will need to rebuild the skin's index by running, npm run reskindex.

You may need to run npm i source-map-loader in matrix-js-sdk if you get errors about "Cannot resolve module 'source-map-loader'" due to shortcomings in webpack.

Deployment

Just run npm build and then mount the vector directory on your webserver to actually serve up the app, which is entirely static content.