2A STRA

This instruction describes how to run Matrix server with custom Element-Web client. Matrix  - Matrix is an open standard for interoperable, decentralized, real-time communication over IP. Element-Web  - A glossy Matrix collaboration client for the web. TL;DR On  repo  development server Clone Element-web source code: userrepo@repo :~$ git clone https://github.com/vector-im/element-web.git Change the code. Build new docker image (tag 0.1): userrepo@repo :~/element-web$ docker build -t repo:5000/myelement:0.1 . Upload created image to local registry: userrepo@repo :~$ docker push repo:5000/myelement:0.1 On  matrix  test server Execute ansible script for automatic build and deploy: root@matrix :~# ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start Prepare local docker registry and git server Configure local registry server OS name: userrepo@repo :~$ uname -a Linux repo 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux Co...

  Challenges  to push custom changes to main source code Core developers mightn’t approve including your changes to main branch. They may have their own rules and vision of product development, or your changes may be not corresponding to the main project goals. So, you need to maintain your custom branch by yourself. Then your changes will not be included to upstream and when new version will be released it will not contain your patches. You will need to patch all new versions again. Complexity of custom branch maintain Since bug fixes and securities patches are made in upstream only, you will need regularly merge changes from main branch to custom. Main code developing will become incompatible with custom changes and create conflicts in a code which hard to resolve. Totally separate from main code developing is too complicated. Core developers’ community could include large number of code contributors which may be much bigger than a local team. Also core development probably ...