|
|
|
|
|
by kusmi
3160 days ago
|
|
I once wrote a thing that would take text files uploaded to the alfresco ecm, containing run options or data input for some automation script sitting on a server that's part of the corporate subnet, and depending on how the text file was tagged or which folder it was in, it would create service and timer unit files for systemd. The files would sync to the server via alfresco's atom API, and any output generated would be uploaded back into alfresco. This was neat because you could make alfresco user accounts for these bots, thereby turning them on or off for any project by simply adding the user and further modify which directories should be crawled for tasks to run by assigning read permissions to the bot account all via the client side alfresco share interface. Server images containing the bot code could be provisioned in say AWS, and integrated into an alfresco cluster. It made it much simpler for allowing non-technical users to run scheduled web crawlers, pipe them into document formatters, for web publication, or attach to email out the results hot to a given email list all from the nice alfresco share interface. |
|