It could break some third party clients that guessed these filenames depending on the video UUID. We'll continue this work in the future
for video filenames, so admins can easily cache these files (using multiple reverse proxies etc)
+### Maintenance
+
+ * Fix nginx max body size configuration
### CLI tools
* More robust channel change federation
* Fix emptying video tags
* Fix broken local actors that do not have a public/private key
+ * Fix bad PeerTube URL for playlist embed
* Live:
* Don't update live attributes if they did not change (allowing to update live metadata even if the live has started)
* Fix live RAM usage when ffmpeg is too slow to transcode the RTMP stream
git checkout develop && rm -r ./node_modules && yarn install --pure-lockfile && npm run build:server
NODE_APP_INSTANCE=6 NODE_ENV=test npm run start
```
- * Run `rm -r node_modules && rm -r client/node_modules && yarn install --pure-lockfile && npm run build` to see if all the supported languages compile correctly
+ * Run `rm -rf node_modules && rm -rf client/node_modules && yarn install --pure-lockfile && npm run build` to see if all the supported languages compile correctly
* Update https://peertube2.cpy.re and check it works correctly
* Check CI tests are green
* Run E2E tests: `BROWSERSTACK_USER=my_user BROWSERSTACK_KEY=my_key npm run e2e`