Skip to main content

Admin Dashboard Quickstart

This document will guide you through setting up the admin dashboard in the Medusa backend.

Overview​

The admin dashboard is installed on the Medusa backend. The admin dashboard starts when you start the Medusa backend. This also means you can later deploy the Medusa backend along with the admin dashboard on the same hosting.

This guide will explain the steps and configurations required to set up the admin dashboard.

Prerequisites​

Medusa Backend​

As the admin dashboard is a plugin installed on the Medusa Backend, you must have a Medusa Backend installed first. You can learn how to install it in this documentation.

Node.js​

The Admin uses Vite v4.1.4 which requires v14.8+ or v16+ of Node.js, and as Medusa requires v16 or greater it's recommended you use v16+ of Node.js.

You can check which version of Node you have by running the following command:

node -v

You can install Node from the official website.

Install and Serve Admin with the Backend​

This section explains how to install the admin to be served with the Medusa Backend and later deployed together.

Step 1: Install the Package​

In the directory of your Medusa backend, run the following command to install admin dashboard:

npm install @medusajs/admin

Installing the @beta version of the admin and Medusa core allows you to perform customizations such as creating Admin Widgets or Admin Dashboard Routes. You can install the beta version with the following command:

npm install @medusajs/admin@beta @medusajs/medusa@beta

Step 2: Add Admin to Medusa Configurations​

In medusa-config.js, add the admin plugin into the array of plugins:

medusa-config.js
const plugins = [
  // ...
  {
    resolve: "@medusajs/admin",
    /** @type {import('@medusajs/admin').PluginOptions} */
    options: {
      // ...
    },
  },
]

The plugin accepts the following options:

  1. serve: (default: true) a boolean indicating whether to serve the admin dashboard when the Medusa backend starts. If set to false, you can serve the admin dashboard using the dev command.
  2. path: (default: app) a string indicating the path the admin server should run on when running the Medusa backend in production. It shouldn't be prefixed or suffixed with a slash /, and it can't be one of the reserved paths: "admin" and "store".
  3. outDir: Optional path for where to output the admin build files.
  4. autoRebuild: (default: false) a boolean indicating whether the admin UI should be rebuilt if there are any changes or if a missing build is detected when the backend starts. If not set, you must manually build the admin dashboard.

Optional: Manually Building Admin Dashboard​

If you have autoRebuild disabled, you must build your admin dashboard before starting the Medusa backend. Refer to the build command for more details.

Step 3: Test the Admin Dashboard​

If you disabled the serve option, you need to run the admin dashboard separately using the dev command

You can test the admin dashboard by running the following command in the directory of the Medusa backend:

npx @medusajs/medusa-cli develop

This starts the Medusa Backend and the admin dashboard. By default, the admin will be available on the URL localhost:9000/app. If you set the path option, then the admin will be available on localhost:9000/<PATH> with <PATH> being the value of the path option.

If you're using the @beta version of the admin plugin, the admin dashboard will run on localhost:7001 when you run the develop command.

Did you set up the admin successfully?

Demo Credentials​

If you installed the demo data when you installed the Medusa backend by running:

npm run seed

You can use the email admin@medusa-test.com and password supersecret to log in.

Passwords in Medusa are hashed using the scrypt-kdf. The password hash is then stored in the database.

Create a New Admin User​

To create a new admin user from the command line, run the following command in the directory holding your Medusa backend:

npx @medusajs/medusa-cli user -e some@email.com -p some-password

This will create a new user that you can use to log into your admin panel.

Build Command Options​

The build command in the admin CLI allows you to manually build the admin dashboard. If you intend to use it, you should typically add it to the package.json of the Medusa backend:

package.json
{
  "scripts": {
    // other scripts...
    "build:admin": "medusa-admin build"
  }
}

You can add the following options to the medusa-admin build command:

  • --deployment: a boolean value indicating that the build should be ready for deployment. When this option is added, options are not loaded from medusa-config.js anymore, and it means the admin will be built to be hosted on an external host. For example, medusa-admin build --deployment.
  • --backend or -b: a string specifying the URL of the Medusa backend. This can be useful with the --deployment option. The default here is the value of the environment variable MEDUSA_BACKEND_URL. For example, medusa-admin build --deployment --backend example.com
  • --out-dir or -o: a string specifying a custom path to output the build files to. By default, it will be the build directory. For example, medusa-admin --deployment --out-dir public.
  • --include or -i: a list of strings of paths to files you want to include in the build output. It can be useful if you want to inject files that are relevant to your external hosting, such as adding a 200.html file that is needed for redirects on Surge. For example, medusa-admin --deployment --include 200.html
  • --include-dist or -d: a string specifying the path to copy the files specified in --include to. By default, the files are coopied to the root of the build directory. You can use this option to change that. For example, medusa-admin --deployment --include 200.html --include-dist static.

Dev Command Options​

The dev command in the admin CLI allows you to run the admin dashboard in development separately from the Medusa backend. If you intend to use it, you should typically add it to the package.json of the Medusa backend:

package.json
{
  "scripts": {
    // other scripts...
    "dev:admin": "medusa-admin dev"
  }
}

You can add the following options to the medusa-admin dev command:

  • --backend or -b: a string specifying the URL of the Medusa backend. By default, it's the value of the environment variable MEDUSA_BACKEND_URL. For example, medusa-admin dev --backend example.com.
  • --port or -p: the port to run the admin on. By default, it's 7001. For example, medusa-admin dev --port 8000.

Admin User Guide​

The admin dashboard provides a lot of ecommerce features including managing Return Merchandise Authorization (RMA) flows, store settings, products, orders, and much more.

You can learn more about the admin dashboard and its features in the User Guide.

Troubleshooting Installation​

Signing into Admin

If you've created a new Medusa backend and used the seed command, the default credentials are:

email: admin@medusa-test.com
password: supersecret

Alternatively, you can create your own users using the Medusa CLI tool:

npx @medusajs/medusa-cli user -e some@email.com -p somepassword

See Also​

CORS Errors

If you are experiencing connection issues when trying to access your Medusa backend from a storefront or the admin dashboard, it is most likely due to Cross-Origin Resource Sharing (CORS) issues.

You might see a log in your browser console, that looks like this:

CORS error log

In your medusa-config.js , you should ensure that you've configured your CORS settings correctly. By default, the Medusa starter runs on port 9000, Medusa Admin runs on port 7000, and the storefront starters run on port 8000.

The default configuration uses the following CORS settings:

medusa-config.js
// CORS when consuming Medusa from admin
const ADMIN_CORS = process.env.ADMIN_CORS || 
  "http://localhost:7000,http://localhost:7001"

// CORS to avoid issues when consuming Medusa from a client
const STORE_CORS = 
  process.env.STORE_CORS || "http://localhost:8000"

If you wish to run your storefront or Medusa admin on other ports, you should update the above settings accordingly.

See Also​

See Also​

Was this page helpful?
© 2023 Medusa, Inc. All rights reserved.