HPCE/gitea-pages
0
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Activity

Update meg docs
All checks were successful
Build and Deploy Documentation / build-and-deploy (push) Successful in 6s
Details

Browse Source
This commit is contained in:
caubet_m
2025-08-07 16:38:32 +02:00
parent b639b38042
commit 0f8c3bb7fe
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pages/meg/99-support/migration-to-merlin7.md
View File

@@ -122,7 +122,7 @@ Options:
-p | --project-name PRJ_NAME Mantadory field. MeG project name. Examples: -p | --project-name PRJ_NAME Mantadory field. MeG project name. Examples:
- 'online' - 'online'
- 'offline' - 'offline'
- 'shared - 'shared'
-F | --force-destination-mkdir Create the destination parent directory (default: false) -F | --force-destination-mkdir Create the destination parent directory (default: false)
Example: mkdir -p $(dirname /data/project/meg/data1/PROJECT_NAME) Example: mkdir -p $(dirname /data/project/meg/data1/PROJECT_NAME)
Result: mkdir -p /data/project/meg/data1 Result: mkdir -p /data/project/meg/data1
@@ -170,7 +170,7 @@ Please confirm to start (y/N):
##### Example: Migrating a Specific Subdirectory ##### Example: Migrating a Specific Subdirectory
The following example demonstrates how to migrate **only a subdirectory**. The following example demonstrates how to migrate **only a subdirectory**. In this case, we use the option `-F` to create the parent directory in the destination, to ensure that this exists before transferring:
⚠️ **Important:** ⚠️ **Important:**
- When migrating a subdirectory, **do not** run concurrent migrations on its parent directories. - When migrating a subdirectory, **do not** run concurrent migrations on its parent directories.