# Making migrations when developing a plugin, I had to do it that way
**URL:** https://community.baserow.io/t/making-migrations-when-developing-a-plugin-i-had-to-do-it-that-way/1312
**Category:** Plugins
**Created:** [September 4, 2022, 4:14am UTC](https://community.baserow.io/t/making-migrations-when-developing-a-plugin-i-had-to-do-it-that-way/1312 "2022-09-04T04:14:54Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@lucw](https://community.baserow.io/u/lucw)
#### Post date: [September 4, 2022, 4:14am UTC](https://community.baserow.io/t/making-migrations-when-developing-a-plugin-i-had-to-do-it-that-way/1312/1 "2022-09-04T04:14:54Z")
the docs here [Field type // Baserow](https://baserow.io/docs/plugins%2Ffield-type) say we should be able to do the following:
```auto
docker-compose run my-baserow-plugin /baserow.sh backend-cmd manage makemigrations
docker-compose run my-baserow-plugin /baserow.sh backend-cmd manage migrate
```
that didn’t work for me. The baserow.sh script kept showing me the help / command list. I found I had to start my all in one container, then make migrations the following way, making sure to specify my app name (baserow\_vocabai\_plugin), otherwise no migrations would be detected.
```auto
docker container exec e214ca3b3644 /baserow.sh backend-cmd manage makemigrations baserow_vocabai_plugin
docker container exec e214ca3b3644 /baserow.sh backend-cmd manage migrate baserow_vocabai_plugin
```
---
### Author:  [@nigel](https://community.baserow.io/u/nigel)
#### Post date: [September 6, 2022, 3:43pm UTC](https://community.baserow.io/t/making-migrations-when-developing-a-plugin-i-had-to-do-it-that-way/1312/2 "2022-09-06T15:43:19Z")
Apologies this is indeed incorrect I will fix shortly 🙂 The correct commands should be:
```bash
docker-compose -f docker-compose.dev.yml run --rm my-baserow-plugin backend-cmd manage makemigrations
docker-compose -f docker-compose.dev.yml run --rm my-baserow-plugin backend-cmd-with-db manage migrate
```