A browser and wallet for LBRY, the decentralized, user-controlled content marketplace.
122d561a20
Ticket: 1189 ## Issue There is a bug in a batched `resolve` that returns jumbled data. Temporarily switch to `claim_search` until that is fixed. ## Notable differences: - `resolve` will tell us directly that a claim has been removed or filtered, so redux will mark the ID as such. `claim_search` simply returns nothing, so we will still end up with an extra `resolve` for these items when the component tries to display it. - The new function currently does not handle Collections (i.e. resolving individual items in the Collection) and Reposts. Given that this is temporarily, I'd like to leave `doClaimSearch` as is, instead of trying to replicate what's in `doResolveUris`. ## Notes: Since we don't care if the resolve fails (and we weren't doing anything in the `catch` anyways), use `finally` instead. |
||
|---|---|---|
| .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 | ||
| 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
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-serverand includes hot-reloading. If you want to debug the web server we use in production you can runyarn dev:web-server. This starts a server atlocalhost:1337and does not include hot reloading.
Customize the web app
- In root directory, duplicate the
.env.defaultfile as.envand make customizations there.cp .env.defaults .env nano .env - To specify your own OG-IMAGE:
- Either place a png named
v2-og.pngin the/customfolder or specify theOG_IMAGE_URLin .env file.
- Either place a png named
- To specify your own channels to be followed on first run:
AUTO_FOLLOW_URLS=lbry://@chan#123...a lbry://@chan2#456...a
- 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.
- Add
- Finally, run
NODE_ENV=production yarn compile:webto rebuild.- Note: You do not need to edit the
.envfile in the/webfolder - that is copied during compilation.
- Note: You do not need to edit the
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