You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2021. It is now read-only.
Firstly, choosing whether to run the just installed application or not is a very common and basic installer option. Almost every installer gives this choice to user.
Secondly, we have a real issue with it: we have custom exchanges plugins in plugins, so when we upgrade RabbitMQ, we loose them. So, after the installation we must only hope messages are not lost (because plugins are unavailable) until we stop RabbitMQ service (and stopping RabbitMQ service just after the start is not trivial at all - it may cause a corruption if RabbitMQ service is not completely started), copy our plugins to plugins and start RabbitMQ service again.
Can this code from windows-exe/rabbitmq_nsi.in be put in a separate command line controlled optional [sub]section?
If you have time to submit a pull request implementing this feature, that would be the fastest way to get it added to RabbitMQ. The NSIS documentation is available here
Firstly, choosing whether to run the just installed application or not is a very common and basic installer option. Almost every installer gives this choice to user.
Secondly, we have a real issue with it: we have custom exchanges plugins in
plugins
, so when we upgrade RabbitMQ, we loose them. So, after the installation we must only hope messages are not lost (because plugins are unavailable) until we stop RabbitMQ service (and stopping RabbitMQ service just after the start is not trivial at all - it may cause a corruption if RabbitMQ service is not completely started), copy our plugins toplugins
and start RabbitMQ service again.Can this code from
windows-exe/rabbitmq_nsi.in
be put in a separate command line controlled optional [sub]section?[168224478]
The text was updated successfully, but these errors were encountered: