This updates and rewrites the supported environments portion of the README. It
also adds a new experimental support tier to clarify how we'll handle things
like installed PWAs and mobile web.
This removes `fetch-develop.deps.sh` from the docs, as it's designed more for
use on CI environments and ends up causing confusion when used for anything
else.
Fixes https://github.com/vector-im/riot-web/issues/11247
The main README is very busy with too much information in one file. This
attempts to clean up one portion by moving configuration docs to a separate
file.
Fixes https://github.com/vector-im/riot-web/issues/9965
Implements the process described here: https://github.com/vector-im/riot-web/issues/9290#issuecomment-481966910
The expectation is that later layers (like the react-sdk) will make use of the `validated_discovery_config` option instead of interpreting the config themselves.
We intentionally block the UI from loading here to avoid races between discovery and the app loading.
change mentions of https://riot.im/packages to https://packages.riot.im
add instructions to remove old, now-untrusted riot.im signing key
update language and move from 'apt-get` to the simpler `apt`
A custom user data directory can now be specified using the "profile-dir"
command line argument.
Github ref: closes#6175
Signed-off-by: Pacien TRAN-GIRARD <pacien.trangirard@pacien.net>
At the current time, we do not intend to do additional work specifically to
support Edge. If it works for most use cases, that's great, but we do not
intend to fix issues that affect only Edge.
Fixes https://github.com/vector-im/riot-web/issues/9201
Most `npm` operations are replaced with `yarn`, which generally has better
behavior. However, steps like publish that write to the NPM registry are left to
`npm`, which currently handles these tasks best.
Take advantage of Yarn's preservation of links while installing and set up links
first and install second. This should result in a small speedup since we no
longer install the published SDKs just to replace them on the next line.
Most `npm` operations are replaced with `yarn`, which generally has better
behavior. However, steps like publish that write to the NPM registry are left to
`npm`, which currently handles these tasks best.
