Hi Jonas, It depends on how sophisticated of a process you need, and on the scale of the project, and the skills of your team.
As you mention, you can use traditional maven produced jars, just include all your resources in a maven jar project. If you want to stick with light modules, which are just a collection of files, then you just need to get those files in a directory to your server. You could pull them directly to the server from your git or other source control repository - either manually or automated with git hooks or other technique to your servers. If you already have a CI server setup, you could integrate it something like this: A CI (continuous integration) server (ie Jenkins) build job is triggered when new updates occur on the light module git repository and compile the files into a .tar.gz and upload them to a repository like Nexus. The build job then executes further automation (eg with Ansible playbook) to connect to the target servers, pull the latest .tgz and unpack them on the server. Magnolia resources system will detect the new files and load them automatically. Just a few approaches. I hope this helps. Cheers, Topher -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=f7a22ade-b1e0-438f-b1fe-432afe7506f4 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
