Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi, I am still struggling with the best deployment method, and I wonder how you do it, probably a new more general issue could be written about it.
Especially I am thinking about the proper way of letting forena know there is a new report file. Not in the database, just copied from the test to production. My wokaround is to save the forena settings - it apparently imports the new files, but seems to do much more (reimporting all other reports even though they havent changed). Probably some subset of the current functionality could be used ?
Also it'd be nice to have a way of checking whether the data blocks the report is reffering to are available ... (another task probably ?)
thanks a lot :).
Comments
Comment #1
metzlerd commentedAm planning on implementing the distribution mechanism using a custom drush command. This will allow you do download an upgraded modules and copy reports from drush scripts.
Comment #2
metzlerd commentedComment #3
metzlerd commentedDrush copy command has been implemented in 7.x-3.x-dev branch.
dursh frxcc will clear the report cache
dursh frxcp will revert module distributed reports to originals.