never tried but according to the doc Q2 supports recursive deploy:
https://github.com/jpos/jPOS/blob/master/doc/src/asciidoc/ch07/running.adoc
Q2 accepts several command line switches; for a complete list, use --help, e.g.:
bin/q2 --help usage: Q2 -C,--config <arg> Configuration bundle -c,--command <arg> Command to execute -d,--deploydir <arg> Deployment directory -e,--encrypt <arg> Encrypt configuration bundle -h,--help Usage information -i,--cli Command Line Interface -n,--name <arg> Optional name (defaults to 'Q2') -O,--osgi Start experimental OSGi framework server -p,--pid-file <arg> Store project's pid -r,--recursive Deploy subdirectories recursively -s,--ssh Enable SSH server -sa,--ssh-authorized-keys <arg> Path to authorized key file (defaults to 'cfg/authorized_keys') -sh,--ssh-host-key-file <arg> ssh host key file, defaults to 'cfg/hostkeys.ser' -sp,--ssh-port <arg> ssh port (defaults to 2222) -su,--ssh-user <arg> ssh user (defaults to 'admin') -v,--version Q2's version
--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/eb9f4870-b4f5-4571-a9a9-3970dfe8cdea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
jPOS does support --recursive
but there is a problem, the directory name will play in the deploy order.
I think we can make some small changes to the --recursive
switch so that we honor the switch and scan all directories but we still sort based on file basename, but, that would also have to be configurable, I can imagine situations where people want to keep the order inside the sub directories. We may add dependency support in the future so that we can get rid of the deploy order (that’s tricky when you redeploy stuff on a running system).
In some systems with many servers I ended up writing a little configurator that reads a YAML file and create the XMLs, so you still have the XMLs in the deploy directory, but they get auto-generated from a single file, i.e:
-
server: server1
port: 2000
channel: NACChannel
header: 6000010000
packager: GenericPackager
packager_config: jar:packager/iso87binary.xml
destination: dest1
filters:
- MyFilter
- MyOtherFilter
-
server: server2
port: 2001
channel: NACChannel
header: 6000010000
packager: GenericPackager
packager_config: jar:packager/iso87binary.xml
destination: dest1
filters:
- MyFilter
- MyOtherFilter
The configurator is implemented as a little jPOS CLI command, so everything gets quite integrated.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+unsubscribe@googlegroups.com.
To post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/eb9f4870-b4f5-4571-a9a9-3970dfe8cdea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/fc9ad2c6-acfa-28b4-a099-4e24b3f1511a%40gmail.com.