This repository has been archived on 2022-10-07. You can view files and clone it, but cannot push or open issues or pull requests.
skynet-webportal/packages/dashboard-v2
Michał Leszczyk 916a420b72
refactor(dashboard-v2): replace pretty-bytes with in-house solution
2022-04-15 16:19:29 +02:00
..
.storybook chore(dashboard-v2): add storybook-addon-gatsby 2022-02-26 13:47:58 +01:00
src refactor(dashboard-v2): replace pretty-bytes with in-house solution 2022-04-15 16:19:29 +02:00
static Dashboard v2 lighthouse scores improvements (#1972) 2022-04-06 11:10:28 +02:00
.eslintignore ops(dashboard-v2): setup Storybook 2022-02-18 09:18:41 +01:00
.eslintrc.js style(dashboard-v2): prettify 2022-02-18 09:20:47 +01:00
.gitignore ops(dashboard-v2): setup Storybook 2022-02-18 09:18:41 +01:00
.prettierignore ops(dashboard-v2): setup Storybook 2022-02-18 09:18:41 +01:00
.prettierrc.json style(dashboard-v2): update prettier config 2022-02-18 09:17:28 +01:00
Dockerfile ops(dashboard-v2): prepare Dockerfile (#1971) 2022-04-07 12:59:20 +02:00
README.md ops(dashboard-v2): improve local developer experience 2022-04-12 12:55:09 +02:00
gatsby-browser.js refactor(dashboard-v2): move access guards outside of SWRConfig 2022-04-11 09:09:39 +02:00
gatsby-config.js ops(dashboard-v2): publish new dashboard under /v2 prefix 2022-04-14 18:30:27 +02:00
gatsby-ssr.js refactor(dashboard-v2): move access guards outside of SWRConfig 2022-04-11 09:09:39 +02:00
package.json refactor(dashboard-v2): replace pretty-bytes with in-house solution 2022-04-15 16:19:29 +02:00
postcss.config.js style(dashboard-v2): prettify 2022-02-18 09:20:47 +01:00
tailwind.config.js feat(dashboard-v2): implement data mutations for API keys 2022-03-25 11:06:21 +01:00
yarn.lock refactor(dashboard-v2): replace pretty-bytes with in-house solution 2022-04-15 16:19:29 +02:00

README.md

Skynet Account Dashboard

Code behind account.skynetpro.net

Development

This is a Gatsby application. To run it locally, all you need is:

  • yarn install
  • yarn start

Accessing remote APIs

To have a fully functioning local environment, you'll need to make the browser believe you're actually on the same domain as a working API (i.e. a remote dev or production server) -- otherwise the browser will block the session cookie. To do the trick, configure proper environment variables in the .env.development file. This file allows to easily control which domain name you want to use locally and which API you'd like to access.

Example:

GATSBY_PORTAL_DOMAIN=skynetfree.net # Use skynetfree.net APIs
GATSBY_HOST=local.skynetfree.net # Address of your local build

It's recommended to keep the 2LD the same, so any cookies dispatched by the API work without issues.

With the file configured, run yarn develop:secure -- it will run gatsby develop with --https -p=443 options. If you're on macOS, you may need to sudo the command to successfully bind to port 443 (https).

Gatsby will automatically add a proper entry to your /etc/hosts file and clean it up when process exits.