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

Question: is this plugin compatible with mina 1.0? #19

Closed
kritop opened this issue Aug 22, 2016 · 4 comments
Closed

Question: is this plugin compatible with mina 1.0? #19

kritop opened this issue Aug 22, 2016 · 4 comments

Comments

@kritop
Copy link

kritop commented Aug 22, 2016

i running into an error executing mina deploy, and wanted to know if its a compatibility issue or another problem

@endoze
Copy link
Owner

endoze commented Aug 22, 2016

I'll have to check it out as I haven't upgraded any of my apps to use mina 1.0 as of yet. If you can post the error you are receiving it could make debugging any potential issues with this plugin much easier.

@kritop
Copy link
Author

kritop commented Aug 22, 2016

thanks!
also just ran into this: mina-deploy/mina#62
does the plugin offer any more features that might consider using it over the default multistage support?

@endoze
Copy link
Owner

endoze commented Aug 22, 2016

It avoids the to= syntax of setting the stage when deploying and uses a task instead. I personally like the syntax of mina production deploy over mina deploy to=production.

The other big difference is that this plugin allows storing your configuration for each stage in separate files and avoids stuffing a case/if statement in your deploy.rb configuration.

The built in support for multistage is really great, this just builds on the same kind of idea with more separation of stage logic.

@endoze
Copy link
Owner

endoze commented Oct 19, 2016

@kritop A heads up that I've just released a new version of this gem that is compatible with mina 1.0. The new version of mina-multistage is 1.0.3. Unless you have any further questions, I'm going to close this issue out. Thanks for your contributions!

@endoze endoze closed this as completed Oct 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants