Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to run migration script from V1 -> V3 #352

Open
jdipallo opened this issue Nov 2, 2022 · 3 comments
Open

How to run migration script from V1 -> V3 #352

jdipallo opened this issue Nov 2, 2022 · 3 comments
Labels

Comments

@jdipallo
Copy link

jdipallo commented Nov 2, 2022

Hello:

We have upgraded an old Meteor JS project (1.3.2.4) to current. This project was using V1 of alaning roles.

Question 1) How can we upgrade from V1 -> V3
2) The documentation to migrate from V1 -> V2 and V2 -> V3 specifies the meteor shell. We don't have Meteor installed in Production therefore no Meteor shell.

As we are barely using Roles, (very simply there are admin's and that's about it), I've examined the roles collection and role-assignment join collection. In my local dev env, I have simply dropped the roles collection, recreated it like the alaning docs specify and then created the role-assignment collection pointing to the userID and corresponding role. This seems to have setup things where everything works. am I missing anything else or any other ideas to assist is running this migration script? And, where can i see the code for this migration script?

Thank you kindly

@leonardoventurini
Copy link

In the past all I have done was run these methods listed here, one after the other in a migration not the shell:

https://github.com/Meteor-Community-Packages/meteor-roles#roles-migration

Roles._forwardMigrate2()
Roles._forwardMigrate3()

They should be available globally I think.

You can use a database migration tool like this one:

https://packosphere.com/percolate/migrations/0.8.6

Hope it helps.

@StorytellerCZ
Copy link
Member

@jdipallo did @leonardoventurini solution work for you?

@jdipallo
Copy link
Author

@StorytellerCZ
Hello. No, that solution didn’t work for me. Simply manually modifying as I described seems to work thus far.
thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants