Added documentation about PartKeepr migration process

This commit is contained in:
Jan Böhmer 2023-03-26 00:32:03 +01:00
parent a48b4ccaa8
commit a4e68ea2d6
5 changed files with 57 additions and 2 deletions

View file

@ -31,6 +31,7 @@ You can get help for every command with the parameter `--help`. See `php bin/con
* `partdb:migrations:convert-bbcode`: Migrate the old BBCode markup codes used in legacy Part-DB versions (< 1.0.0) to the new markdown syntax
* `partdb:attachments:clean-unused`: Remove all attachments which are not used by any database entry (e.g. orphaned attachments)
* `partdb:cache:clear`: Clears all caches, so the next page load will be slower, but the cache will be rebuild. This can maybe fix some issues, when the cache were corrupted. This command is also needed after changing things in the `parameters.yaml` file or upgrading Part-DB.
* `partdb:migrations:import-partkeepr`: Imports an mysqldump XML dump of a PartKeepr database into Part-DB. This is only needed for users, which want to migrate from PartKeepr to Part-DB. *All existing data in the Part-DB database is deleted!*
## Database commands
* `php bin/console doctrine:migrations:migrate`: Migrate the database to the latest version

View file

@ -16,6 +16,8 @@ Part-DB offers the possibility to import existing data (parts, datastructures, e
> administrators. If you want to allow other users to import data, or can not import data, check the permissions of the user. You can enable import for each data structure
> individually in the permissions settings.
If you want to import data from PartKeepr you might want to look into the [PartKeepr migration guide]({% link upgrade_legacy.md %}).
### Import parts
Part-DB supports the import of parts from CSV files and other formats. This can be used to import existing parts from other databases or datasources into Part-DB. The import can be done via the "Tools -> Import parts" page, which you can find in the "Tools" sidebar panel.