🦑 Current and upcoming map schedules for Splatoon 2
Go to file
Unknown 5fa3c1110d Remove weapon update code
This was used for the Salmon Run admin dialog, but that's no longer needed since Salmon Run schedules are now available via SplatNet. Removing this for now since I don't really need the weapons database anywhere now and since I'm going to refactor the SplatNet updater.
2017-11-24 13:47:30 -08:00
docker Add no-cache header for the data directory 2017-11-18 14:19:59 -08:00
src Remove weapon update code 2017-11-24 13:47:30 -08:00
.babelrc Initial commit 2017-08-02 09:58:58 -07:00
.env.example Change updater to use separate accounts for each region 2017-11-09 16:15:29 -08:00
.gitattributes Initial commit 2017-08-02 09:58:58 -07:00
.gitignore Add nginx container for use with nginx-proxy 2017-10-27 17:32:44 -07:00
docker-compose.override.yml.example Fix example override file name 2017-10-27 18:01:46 -07:00
docker-compose.yml Add nginx container for use with nginx-proxy 2017-10-27 17:32:44 -07:00
license.txt Add license 2017-08-15 16:50:29 -07:00
package.json Retrieve Salmon Run schedule details from SplatNet 2017-11-09 09:27:27 -08:00
postcss.config.js Use CSS autoprefixer 2017-08-15 16:50:29 -07:00
readme.md Restructure data updater 2017-08-16 13:07:16 -07:00
webpack.config.js Add page screenshot generator 2017-09-20 10:43:10 -07:00
yarn.lock Retrieve Salmon Run schedule details from SplatNet 2017-11-09 09:27:27 -08:00

Splatoon2.ink

Splatoon2.ink shows the current and upcoming map schedules for Splatoon 2.

This site was built with Vue.js and Bulma. All data comes from the SplatNet 2 API.

More information about Nintendo's API can be found here.

Note: The Splatnet updater script requires Node.js v8 or later.

Getting Started

Clone this repo:

git clone git@github.com:misenhower/splatoon2.ink.git

Next, copy .env.example to .env and update its values.

cp .env.example .env

You can retrieve your iksm_session ID value (NINTENDO_SESSION_ID inside .env) using Fiddler or a similar tool. See here for further instructions.

I recommend using Yarn to manage JS dependencies.

yarn install    # Install dependencies
yarn splatnet   # Retrieve updates from Splatnet and the Salmon Run calendar
yarn serve      # Start the webpack dev server

Data retrieved from Splatnet is stored in the public/data directory.

By default, the dev server will run on port 8080. When running yarn serve you can access the site by going to http://localhost:8080.

Production

Build minified assets for production:

yarn build

Retrieve updates from Splatnet every hour via node-cron:

yarn cron

Docker

I use a Docker container on my production server to build production assets and retrieve data from Splatnet.

sudo docker-compose run --rm app yarn build     # Build production assets
sudo docker-compose up -d app                   # Start periodic updates