6bd384b01a
## Background Per developer of `tus-js-client`, it is normal to occasionally encounter upload errors. The auto-retry mechanism is meant to address this. While implementing tab-lock to prevent multiple uploads of the same file, 423_locked was used to detect this scenario. But 423_locked could also mean "the server is busy writing the chunk" (per discussion with Randy), so we kind of disabled the auto-retry mechanism accidentally. Meanwhile, from a prior discussion with Randy, one of the chunk-writing duration took 3 minutes. Our current maximum of "retry after 15s" wouldn't help. ## Change 1. Given that tab-locking was improved recently and no longer reliant on the server error messages (we use secure storage to mark a file as locked), reverted the change to "skip retry on 409/423". This is now back to normal recommended behavior. 2. `tus-js-client` currently does not support variable retry delay, otherwise we could prolong the delay if the error was 423. Since we know it could take up to 3 minutes, and that we don't know if it's file-size dependant, just add another 30s retry and put a friendlier message asking the user to retry themselves after waiting a bit. |
||
|---|---|---|
| .github | ||
| .tx | ||
| build | ||
| custom | ||
| electron | ||
| extras | ||
| flow-typed | ||
| homepages | ||
| static | ||
| ui | ||
| web | ||
| .env.defaults | ||
| .eslintignore | ||
| .eslintrc | ||
| .flowconfig | ||
| .gitignore | ||
| .lintstagedrc.json | ||
| .prettierrc.json | ||
| .sentryclirc | ||
| babel.config.js | ||
| CHANGELOG.md | ||
| config.js | ||
| CONTRIBUTING.md | ||
| electron-builder.json | ||
| LICENSE | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| webpack.base.config.js | ||
| webpack.electron.config.js | ||
| yarn.lock | ||
Odysee Frontend - Odysee.com
This repo contains the UI and front end code that powers Odysee.com.
Table of Contents
Usage
Go to the website to interact on this frontend.
Running from Source
You can run the web version (odysee.com), via running onto your host machine, or go to the website itself.
Prerequisites
- Clone (or fork) this repository:
git clone https://github.com/OdyseeTeam/odysee-frontend - Change directory into the cloned repository:
cd odysee-frontend - Install the dependencies:
yarn
Run the web app for development
yarn dev:web
- This uses webpack-dev-server and includes hot-reloading. If you want to debug the web server we use in production you can run
yarn dev:web-server. This starts a server atlocalhost:1337and does not include hot reloading.
Customize the web app
- In root directory, duplicate the .env.default file and rename it to .env then copy the code below and paste it anywhere in the .env file.
cp .env.defaults .env
nano .env
-
To specify your own OG-IMAGE You can either place a png named v2-og.png in the /custom folder or specify the OG_IMAGE_URL in .env
-
To specify your own channels to be followed on first run
AUTO_FOLLOW_URLS=lbry://@chan#123...a lbry://@chan2#456...a -
If you want to customize the homepage content
- add
CUSTOM_HOMEPAGE=trueto the '.env' file - copy
/custom/homepage.example.jsto/custom/homepage.jsand make desired changes tohomepage.js
- If you want up to two custom sidebar links:
PINNED_URI_1=@someurl#2/someclaim#4
PINNED_LABEL_1=Linktext
PINNED_URI_2=$/discover?t=tag&[queryparams]
PINNED_LABEL_2=OtherLinkText
- Finally
NODE_ENV=production yarn compile:webto rebuild Note: You don't need to edit the .env file in the /web folder - that is copied during compile.
Deploy the web app (experimental)
- Create a server with a domain name and a reverse proxy https to port 1337.
- Install pm2, node v10, yarn
- Clone this repo
- Make any customizations as above
- Run
yarnto install - Run
NODE_ENV=production yarn compile:webto build - Set up pm2 to start ./web/index.js
Resetting your Packages
If the app isn't building, or yarn xxx commands aren't working you may need to just reset your node_modules. To do so you can run: rm -r node_modules && yarn or del /s /q node_modules && yarn on Windows.
If you really think something might have gone wrong, you can force your repo to clear everything that doesn't match the repo with git reset --hard HEAD && git clean -fxd && git pull -r
Contributing
We ❤️ contributions from everyone and contributions to this project are encouraged, and compensated. We welcome bug reports, bug fixes and feedback is always appreciated. For more details, see CONTRIBUTING.md.
License
This project is MIT licensed. For the full license, see LICENSE.
Security
For security issues, please reach out to security@odysee.com