4954de2a96
This is a very big commit that does an initial job of upgrading everything to the latest version. TSLint gets replaced by ESLint. Instead of plain node, now ts-node is being used. Old modules also get replaced with new ones (mostly ng2 to ngx). Also obsolete configs have been replaced with how it's used today with Angular. This includes: * Upgrade to: ** Angular 12 ** Typescript 4 ** ESLint 7 and replace TSLint ** Bootstrap 5 ** Eerything connected to these * Run with ts-node * Convert wepack config to angular config * Remove typescript-ioc * Update tsconfigs * Run a git command instead of using a library for sshort hash * Move assets to a new location align with default Angular settings * Database migration for new avatarUrl locations * Simplify Model extension align with newest sequelize version * Remove breadcrumb hack * Fix homeserver typo * A few general fixes that are necessary with newest Typescript rules * Define Express.User interface |
||
|---|---|---|
| config | ||
| docs | ||
| scripts | ||
| src | ||
| web | ||
| .dockerignore | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .travis.yml | ||
| angular.json | ||
| DEVELOPMENT.md | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| karma.conf.js | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| proxy.conf.json | ||
| README.md | ||
| tsconfig.app.json | ||
| tsconfig.backend.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
An open source integration manager for matrix clients, like Element. For help and support, please visit us in #dimension:t2bot.io on Matrix.
Installing Dimension / Running your own
See docs/installing.md for more information on running Dimension.
"Could not contact integrations server" error
- Check that federation is enabled and working on your homeserver. If you're not intentionally running Dimension in a non-federated environment, make sure that your homeserver is configured correctly. If you are running in a non-federated environment, consult docs/unfederated.md.
- Check your SRV records and .well-known delegation. If you are using SRV records to point to your federation port, make sure that the hostname and port are correct, and that HTTPS is listening on that port. Dimension will use the first record it sees and will only communicate over HTTPS. If you're using .well-known delegation for federation, double check that is set up correctly.
- Verify the homeserver information in your configuration. The name, access token, and client/ server API URL all need to be set to point towards your homeserver. It may also be necessary to set the federation URL if you're running a private server.
- Run the troubleshooter. If you're on Element, type
/addwidget https://dimension.t2bot.io/widgets/manager-testin a private room then click the button.
Do I need an integrations manager?
Integration managers aim to ease a user's interaction with the various services a homeserver may provide. Often times the integrations manager provided by Element, is more than suitable. However, there are a few cases where running your own makes more sense:
- Wanting to self-host all aspects of your services (client, homeserver, and integrations)
- Wanting to advertise custom bots specific to your homeserver
- Corporate or closed environments where the default integration manager won't work
How do integration managers work?
Integration managers sit between your users and your integrations (bots, bridges, etc). It helps guide users through the configuration of your integrations for their rooms. The integrations manager can only manage integrations it is configured for. For example, Modular can only provide configuration for the bridges and bots running on matrix.org, while Dimension can provide configuration for your own bots and bridges.
The infrastructure diagram looks something like this:
Development
For more information about working on Dimension, see DEVELOPMENT.md.
License
For information about Dimension's license, please see the LICENSE file included in this repository.