#Clone the Admin UI as a separate project

1 messages · Page 1 of 1 (latest)

toxic zenith
#

Please note that this was the solution I found to run the project separately. Your work environment may require a different configuration. Feel free to include your opinion or changes as appropriate.

  1. Clone the Medusa project (I used the tag v1.20.7), go to packages/admin-ui, if you cannot find the folder, verify that you are in the indicated branch or tag.

  2. The content inside admin-ui will be our project.

If you have already installed the packages, you will need to delete the node_modules folder (rkmdir node_modules).

  1. We update the packages:
npx ncu -u
npm install```

4. Update yarn or install it if you don't have it:
`npm install -g yarn@latest`

5. Change package version:
`"@tanstack/react-query": "^4.22.0"`

6. Finally we create the file with the environment variables:
```//.env
MEDUSA_BACKEND_URL="http://localhost:9000"
ADMIN_PATH="http://localhost:9000"```

**To consider:**
-If you create it in your Medusa backend with the `admin-ui`, you will have conflicts over port `7001 `in your local environment, for this you can do one of the following two options:
   - Disable the UI on the backend from using port `7001`
   - In your admin panel project (the clone), change the default port `7001 `to something like `7002`. If you use `VSCode `you can do (`ctrl + shift + f`) and search for `7001`, so you can change the port faster in the places used
azure token
#

Hi @toxic zenith ! Thanks for detailing out some steps! I've been trying to get this running locally but still running into issues with the dependencies and resolving references to other medusa files.

To confirm, all of the install commands you're running are within the packages/admin-ui directory?

In general when I try to start the app, it seems like can't resolve the medusa dependencies... so I'm wondering if I'm running it from the wrong dir?..

toxic zenith
toxic zenith
wheat gorge
#

@dreamy hearth

split pier
opaque socket
jagged cedar
#

Is it applicable to V2?

hidden tinsel
#

I fully support the idea of making admin_ui a separate project

toxic zenith
#

Now in the afternoon I made a public repository with the admin-ui that I have separately.
But mostly the problem arises in the versions of the packages that are outdated and even if they are updated there are some that must have a specific version for functionality.

toxic zenith