In your gulp setup, create a websocket server and basically make that server publish messages everytime aemsync is triggered to push content to AEM. I have not used the tools you are mentioning, but since you are using gulp and aemsync, you could do the following: But it should give you an alternative to the other tools that exist and get you half way there. Please make sure that LiveReload 2.3 (or later) or another compatible server is running.Ĭan anyone help me figure this out as i'd really like to get it working to streamline my workflow.ĭISCLAIMER: This answer is based on a setup I had working at some point, and by no means is a complete/working answer. That still doesn't work, and when i click the chrome browser extension to sync it i get the following message:Ĭould not connect to LiveReload server. That didn't work, so i got one of our DevOps engineers to open port 35729 (which is the default for Livereload) on the AEM instance. ![]() installing the RemoteLiveReload chrome extension (the AEM instance is hosted on AWS).installing ACS AEM tools package on the AEM instance.installing Netty package on AEM instance.I have tried to follow both these 2 online guides: A have a gulp task watching the js and css that runs gulp-aemsync fine (changes are on the site when i refresh), but being a bit lazy as i am it would be nice to get live reload working so that i never have to manually refresh the page while working. I am using the gulp-aemsync plugin to sync my css and js changes to a clientlib on an AEM instance.
0 Comments
Leave a Reply. |