This repository has been archived on 2023-10-27. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
2023-10-17 21:42:37 +01:00
public fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
src fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
.gitignore fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
LICENSE.md fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
netlify.toml fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
package.json fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
README.md fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
rollup.config.js fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
tsconfig.json fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00
yarn.lock fork from scoresaber-reloaded 2023-10-17 21:42:37 +01:00

ScoreSaber Reloaded

Netlify Status

Users

Just go to ssr.motzel.dev

Devs

Install the dependencies

yarn install

Configure Netlify account

Create a new Netlify project and link it to the forked repo.

Install netlify dev CLI

npm install netlify-cli -g

Then start Netlify dev environment

netlify dev

Navigate to localhost:8888. You should see app running.

Building and running in production mode

By default, Netlify builds the app after every change to the master branch in the repository, so all you need is

git push

... but I don't use Netlify

Check your hosting provider's documentation.

Note that the project uses Netlify redirects to bypass CORS issues in the Beat Savior API and to fetch some of the ScoreSaber subpages (not all data is available in the SS API yet).

Check the contents of netlify.toml and see how you can resolve this with your provider.