saleor-dashboard/README.md

190 lines
4.8 KiB
Markdown
Raw Normal View History

2022-08-19 08:32:21 +00:00
![Saleor Dashboard](https://user-images.githubusercontent.com/44495184/185379472-2a204c0b-9b7a-4a3e-93c0-2cb85205ed5e.png)
<div align="center">
<h1>Saleor Dashboard</h1>
</div>
<div align="center">
<p>A GraphQL-powered, single-page dashboard application for <a href="https://github.com/saleor/saleor">Saleor</a>.</p>
</div>
<div align="center">
<a href="https://saleor.io/">🏠 Website</a>
<span></span>
<a href="https://docs.saleor.io/docs/3.x/">📚 Docs</a>
<span></span>
<a href="https://saleor.io/blog/">📰 Blog</a>
<span></span>
<a href="https://twitter.com/getsaleor">🐦 Twitter</a>
</div>
2019-06-19 16:09:48 +00:00
2019-09-22 12:30:10 +00:00
## Demo
2020-10-13 11:05:07 +00:00
See the [public demo](https://demo.saleor.io/dashboard/) of Saleor Dashboard!
2019-09-22 12:30:10 +00:00
Or launch the demo on a free Heroku instance.
[![Deploy](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy)
2019-06-19 16:04:50 +00:00
## Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
### Prerequisites
2022-11-21 10:52:35 +00:00
- Node.js v18+
2021-10-11 06:53:22 +00:00
- A running instance of [Saleor](https://github.com/saleor/saleor/).
2019-06-19 16:04:50 +00:00
### Installing
Clone the repository:
```
2021-10-11 06:53:22 +00:00
$ git clone https://github.com/saleor/saleor-dashboard.git
2019-06-19 16:04:50 +00:00
```
2020-02-03 11:53:51 +00:00
Enter the project directory:
```
$ cd saleor-dashboard
```
2020-01-22 14:51:33 +00:00
#### Using stable release
2022-09-06 08:21:35 +00:00
Check [release log](https://github.com/saleor/saleor-dashboard/releases/) for the latest release
2020-01-22 14:51:33 +00:00
#### Using development version
If you want to use the latest development version, checkout to the `main` branch:
2020-01-22 14:51:33 +00:00
```
$ git checkout main
2020-01-22 14:51:33 +00:00
```
2019-06-19 16:04:50 +00:00
Install NPM dependencies:
```
2019-06-19 16:06:12 +00:00
$ npm i
2019-06-19 16:04:50 +00:00
```
2019-06-19 14:40:52 +00:00
2019-06-19 15:41:42 +00:00
### Configuration
2019-06-19 14:40:52 +00:00
Create `.env` file in a root directory or set environment variables with following values:
2019-06-19 16:04:50 +00:00
2019-09-22 12:30:10 +00:00
- `API_URI` (required) - URI of a running instance of Saleor GraphQL API.
If you are running Saleor locally with the default settings, set `API_URI` to: `http://localhost:8000/graphql/`.
Make sure that you have `/` at the end of `API_URI`.
2019-06-19 16:04:50 +00:00
2019-09-22 12:30:10 +00:00
- `APP_MOUNT_URI` - URI at which the Dashboard app will be mounted.
E.g. if you set `APP_MOUNT_URI` to `/dashboard/`, your app will be mounted at `http://localhost:9000/dashboard/`.
2019-06-19 14:40:52 +00:00
2019-12-04 10:25:51 +00:00
- `STATIC_URL` - URL where the static files are located.
E.g. if you use S3 bucket, you should set it to the bucket's URL. By default Saleor assumes you serve static files from the root of your site at `http://localhost:9000/`.
2019-06-19 15:41:42 +00:00
### Development
2019-06-19 14:40:52 +00:00
2019-06-19 16:04:50 +00:00
To start the development server run:
```
$ npm start
2019-06-19 16:04:50 +00:00
```
In case you see CORS errors make sure to check [CORS configuration](https://docs.saleor.io/docs/3.x/developer/running-saleor/configuration#allowed_client_hosts) of your Saleor instance or CORS settings in the Cloud Console.
2019-06-19 14:40:52 +00:00
2019-06-19 15:41:42 +00:00
### Production
2019-06-19 14:40:52 +00:00
2019-06-19 16:04:50 +00:00
To build the application bundle run:
```
2019-06-19 16:06:12 +00:00
$ npm run build
2019-06-19 16:04:50 +00:00
```
2020-05-19 08:52:44 +00:00
### Error Tracking
Saleor Dashboard is using a generic error tracking wrapper function that takes care of the most popular use cases:
- initializing the tracker
- capturing exceptions and (optionally) displaying the event id
- setting basic user data (this is opt-in and disabled by default)
By default it ships with a Sentry adapter but any kind of error tracking software can be used by creating a custom adapter (using Sentry and TS types as an example).
Example:
```javascript
// src/services/errorTracking/index.ts
import { CustomAdapter } from "./adapters/";
const errorTracker = ErrorTrackerFactory(CustomAdapter(config));
```
### Running e2e tests
Add Cypress specific env variables to `.env` file (created in configuration section above):
```
CYPRESS_USER_NAME=
CYPRESS_USER_PASSWORD=
CYPRESS_SECOND_USER_NAME=
CYPRESS_PERMISSIONS_USERS_PASSWORD=
CYPRESS_mailHogUrl=
STRIPE_SECRET_KEY=
STRIPE_PUBLIC_KEY=
// not required
CYPRESS_RECORD_KEY= // if you want your local runs recorded
```
For values of those variables refer to our internal documentation.
You are ready to run cypress commands like:
```shell
npm run cy:open
```
### Usage with docker
Build docker image:
```shell
docker build --tag saleor-dashboard .
```
Run nginx from docker and bind it to port on your machine (in this example 8080):
```shell
docker run --publish 8080:80 --env "API_URL=<YOUR_API_URL>" saleor-dashboard
```
Enter `http://localhost:8080/` to use dashboard.
If you want to dynamically change `API_URL` in runtime you can use (assuming you have running container named `saleor-dashboard`):
```shell
docker exec -it -e API_URL=NEW_URL saleor-dashboard /docker-entrypoint.d/50-replace-api-url.sh
```
### Usage with Sentry adapter
Sentry is used as the default tracker so no changes in code are necessary and the configuration is done via environment variables.
The following environment variables are available:
```
# Required
SENTRY_DSN=
# Optional
# https://docs.sentry.io/product/cli/configuration/
SENTRY_AUTH_TOKEN=
SENTRY_ORG=
SENTRY_PROJECT=
SENTRY_URL_PREFIX=
ENVIRONMENT=
```
#### Crafted with ❤️ by [Saleor Commerce](https://saleor.io)