Versioning in Tapestry is really easy. Just increment the version-nr in appModule and you're set. However, I'd like my assets to live on a CDN. (Amazon S3 + cloudfront) . For this to work (along with versioning) I would have to do 2 conceptual things: 1. export assets to a specific s3 bucket linked to cloudfront. 2. point html-code to correct path.
To do this manually I'd have to: - up the version in appmodule by hand. - create a new s3 bucket by hand (with the version-nr encoded in it) - ? copy/ move the versioned assets-directory created by Tapestry to the newly created S3- bucket ( I assume it is created on-the-fly on run-time and are saved to disk? - point html-code to the new correct path. I assume I can code this once, bc. I must be able to access the versionnr, and along with the static s3-path be able to create the path to the newly created s3-bucket. All this is possible, but I would like it to be automated. Is this already possible (with some minor tweaking) If not, where would I start looking to automate this? any pointers highly appreciated. Best regards, Geert-Jan -- View this message in context: http://n2.nabble.com/T5-some-automagical-way-to-export-versioned-assets-to-CDN-tp4437084p4437084.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
