f433287bb6
* fix(dashboard-v2): fix current usage graph on portals without Stripe configured * ops(dashboard-v2): publish new dashboard under /v2 prefix * ops(dashboard-v2): fix SkynetClient on multi-server portals * fix(dashboard-v2): fix skylinks validation for sponsor keys * ops(dashboard-v2): don't actually launch the new dashboard yet :) * chore(dashboard-v2): cleanup console.log call * fix(dashboard-v2): always set portal domain for SkynetClient |
||
|---|---|---|
| .. | ||
| .storybook | ||
| src | ||
| static | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.json | ||
| Dockerfile | ||
| README.md | ||
| gatsby-browser.js | ||
| gatsby-config.js | ||
| gatsby-ssr.js | ||
| package.json | ||
| postcss.config.js | ||
| tailwind.config.js | ||
| yarn.lock | ||
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 installyarn 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.