Could someone provide advice? Should I use DB or stick with local files?

[Ryan Trusty]

I have been asked to integrate Rundeck with a MySQL database.   The reason this is desired is to make it easier to query info about jobs that have run (the requestor wants to run an automated query that lists failed jobs).

We are a MySQL shop and starting a database is not a problem, but I wonder if this is considered a "best practice" for Rundeck.     Are there any pluses/minuses to this, as opposed to sticking with the default file-based storage?

CONFIDENTIALITY NOTICE

The attached information is PRIVILEGED AND CONFIDENTIAL and is intended only for the use of the addressee named above.  If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, please be aware that any dissemination, distribution or duplication of this communication is strictly prohibited. If you receive this communication in error, please notify us immediately by telephone, delete the message and destroy any printed copy of the message. Thank you.

[Alex Honor]

Hi Ryan,

We strongly encourage you to use Mysql rather than the H2 database for production use. Mysql will be faster and scales better.

Thanks

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Alex Honor

[SimplifyOps, Inc | a...@simplifyops.com ]

Be sure to comment and vote on Rundeck Feature Development!