|
1 | 1 | Convert postgresql to filestorage |
2 | 2 | ================================= |
3 | 3 |
|
4 | | -In test and production the plone.org website stores the content data in a |
| 4 | +In test and production the website stores the content data in a |
5 | 5 | Postgresql database using the relstorage driver. If you want to create |
6 | 6 | a local filestorage copy of the data to use for local development, you |
7 | 7 | can use the zodbconvert utility. |
8 | 8 |
|
9 | | -First make sure you are running a local postgresql server with the Plone |
10 | | -content database. The zodbconvert config file assume you use the (datbase) |
11 | | -settings as configured in the docker-compose.yml in the project root. This |
12 | | -compose file starts a local postgresql container on 127.0.0.1:5432 with |
13 | | -ploneorg/ploneorg/ploneorg as the database/role/password . |
| 9 | +First make sure you are running a local postgresql server with the site |
| 10 | +content database. The zodbconvert config file assume you use the (database) |
| 11 | +settings as configured in the postgres-compose.yml in the project root. This |
| 12 | +compose file starts a local postgresql container on 127.0.0.1:5432 |
14 | 13 |
|
15 | 14 | zodbconvert writes the data to the ./data directory in the project root, |
16 | 15 | inside ./data/filestorage and ./data/blobs . |
17 | 16 |
|
18 | 17 | Now run zodbconvert from the project root: |
19 | 18 |
|
20 | | -> ./backend/bin/zodbconvert ./devops/zodbconvert/relstorage.cfg |
| 19 | +> ./backend/bin/zodbconvert ./devops/zodbconvert/from-relstorage.cfg |
21 | 20 |
|
22 | | -This can take 5-15 minutes, depending on your machine specs. |
| 21 | +This can take some minutes, depending on your machine specs. |
23 | 22 |
|
0 commit comments