Skip to main content

2 posts tagged with "grunt"

View All Tags

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 2 min read
Stephan Hochdörfer

A couple of weeks ago I blogged about my experiment with Grails and AngularJS. When I deployed the application "in production" I realized that I needed to change the Urls for accessing the Grails backend. In development mode Grails is running in an own Tomcat instance on a different port, while in production the Grails backend and the AngularJS frontend application are both served from the same Tomcat instance. In fact, both parts get exported to one .war file. After a bit of research I came across the grunt-ng-constant task which is named to be a "plugin for dynamic generation of angular constant modules". Sounds like what I needed ;)

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 2 min read
Stephan Hochdörfer

For more than 1,5 years I rely on reveal.js for my presentations and so far the setup works quite fine for me. However there was one thing which I wanted to change: After launching the built-in webserver via Grunt I needed to launch my browser (Chrome) manually. To sharpen my Grunt skills I went out to find a solution. In the end it turned out to be rather simple ;) - I came across the grunt-open package which allows us to "open urls and files from a grunt task". This is how I set things up: