I'm currently using Odoo version 15 on Odoo.sh and I have a staging branch.
I need to keep that staging branch separately when my migration process is happening.
I know normally when we request to start the migration test they will create a staging branch for that. What I need to know is are they going to use my existing staging branch or they will create a separate new staging branch for this specifically ?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Księgowość
- Zapasy
- PoS
- Project
- MRP
To pytanie dostało ostrzeżenie
3
Odpowiedzi
1688
Widoki
Hi,
If you have only one staging branch as per your subscription, the existing staging branch will be used or have to be used for migration.
If you dont want to touch it, get an extra staging branch and initiate the migration there. If you dont need to pay for extra staging, take a backup of current staging db, initiate the migration in this branch and once the live migration is succeeded bring back this staging db via restore
Thanks
When you request a migration test on Odoo.sh, Odoo typically creates a separate new staging branch specifically for the migration process. They will not use your existing staging branch for this purpose. This way, your existing staging branch remains untouched and can continue to be used separately from the migration process.
Hi Sachitha
The easy way to tackle this issue is take a backup of your staging branch and reload after the upgrade or increase the count of the staging branch
Regards..
Podoba Ci się ta dyskusja? Dołącz do niej!
Stwórz konto dzisiaj, aby cieszyć się ekskluzywnymi funkcjami i wchodzić w interakcje z naszą wspaniałą społecznością!
Zarejestruj się| Powiązane posty | Odpowiedzi | Widoki | Czynność | |
|---|---|---|---|---|
|
1
sty 24
|
2144 | ||
|
2
sie 25
|
3172 | ||
|
1
sty 25
|
1146 | ||
|
1
mar 24
|
2198 | ||
|
CVE-2023-44487 vulnerability
Rozwiązane
|
|
2
paź 23
|
3391 |
