This fetches other front-end tools you may wish to use.

Again there are a whole heap of uses for front-end devs and it will be exciting to see what the future holds for Grunt.įinally, Bower is a front-end package manager which is built by the guys over at Twitter and runs on NodeJS. Other common workflows are to use it is a build runner, and for CSS and JS files to be minified and concatenated together, along with tasks such as running all images though an image minifier to ensure all images are optimised and compressed for the best browsing experience. So front-end devs can run tasks such as 'Watch', which will automatically monitor file changes to Sass and CoffeeScript source files which are then automatically re-compiled into CSS and JavaScript files and then the browser is reloaded. You can compare this as an equivalent to your C# MSBuild workflows. This is because Grunt is a task runner for their front-end workflows.

Grunt is whats all the front-end devs are getting excited about at the moment. It also gives some extra functionality to your Sass files, for example, providing the power to automatically create a sprite image and use it in your CSS - It's voodoo magic!! Next onto Compass, this is seen as a common and useful extension to the popular CSS preprocessor Sass. So from what I can tell your imagination is the only limit with NodeJS and it's worth browsing the NPM repository, to see what other people are up to. Some clever bods have also written Grunt and Bower in NodeJS hence the need for it in this scenario. This is a Javascript application framework which allows you to build a whole range of applications ranging from a HTTP server written in Javascript, to slightly more geeky things such as controlling Parrot's AR Drone. So as I am still new to these front-end toolsets I'll try my best to explain them. What are NodeJS, Compass, Grunt and Bower?īefore I go onto explain this, I'd just like to add a disclaimer that I claim to be no expert in this field and someone with more experience with these tools may give a better explanation of their use. There are plenty of scenarios and ideas that can be set up to fit your team's development workflow. With TeamCity you can be as simple or fancy as you like, involving build steps that copy files from one place to another or running complex tasks such as utilising tools to help you migrate databases from one environment to another. You can then be sure that a working site is deployed. This allows the code to be checked, ensuring the code compiles and builds, as it would inside Visual Studio. In our case at Cogworks, a website in our development environment. TeamCity allows the development team to push to a Git repository and for the TeamCity tool to monitor the Git repository and perform a series of build steps for the website to be built and deployed to a web server. TeamCity is a tool developed by JetBrains to run a continuous integration environment. Generate Free SSL Certificates and Bind It to Azure Webapp With DevopsĪll posts What is TeamCity and Continuous Integration? How to Setup a Private NuGet Feed in Azure DevOps Pipelines If this is closer to your stack (or you just want to know more) check out our Azure tutorials and other blog posts. CogUpdate 2020: Over time, we decided to end our journey with TeamCity and move to the cloud-based Azure DevOps which was closer to our development stack.

Download teamcity