Setup Other: Difference between revisions

Setup Other (view source)

1,198 bytes added , 5 years ago

m

31,003

edits

@@ Line 248: / Line 248: @@
 [[#Top|(back to top)]]
+=Cron module=
+* CRON_DISABLE_KEY_CHANGE ► When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]].
+* CRON_DISABLE_TUTORIAL_CRON ► Disable the tutorial about how to install the cron script (on a SaaS hosting, this should be done by the web hosting provider)
+* CRON_WARNING_DELAY_HOURS ► Set this value to the frequency ou set for the cron script (so a warning will be shown to user to warn it about max frequency of its scheduled jobs)
+[[#Top|(back to top)]]
 =Direct Debit Orders=