5 ms·

It's a build requirement, not a requirement to run the app. If you know a better way to install grunt-contribs, please tell me. I made it more obvious in the r

by xrstf 12y ago

It's a build requirement, not a requirement to run the app. If you know a better way to install grunt-contribs, please tell me. I made it more obvious in the readme that you do not need build tools to run Hosty. Seems like that confused a lot of people.

krapp 12y ago
> If you know a better way to install grunt-contribs, please tell me. I would just not use grunt. I understand it's not required to run it, but even as a build dependency, unless you already have Node installed and running, it's a lot of overhead for relatively little benefit, I think.
- arenaninja 12y ago
  I'm on the fence on this one. On one hand, I'm fond of package managers. On the other, there's a TON of crap every time I run bower install... I've yet to figure out the best way of doing things. I'm thinking of using bower-installer, ship with a copy of the assets, and include bower.json, but not bower_components/. The other alternative is obviously CDNs, but then you're maintaining assets manually
  - krapp 12y ago
    PHP already has a package manager though (Composer.) Granted, the amount of friction involved depends on personal preference, and whatever environment you're working in, but why require a package manager in another language (and, potentially, the language itself) when one exists for the language you're actually deploying in?
    - girvo 12y ago
      I'm sympathetic to your point. Where I work, we use Grunt and npm for our PHP projects, and I'm in the process of replacing them (slowly but surely) with PHP-based versions of the tools we use, and replacing Gruntfiles with Makefiles. It's experimental, currently, but I feel like it's doable. The only dependency then is PHP and Composer, which I think is nice.
  - bombtrack 12y ago
    I include bower_components/ in .gitignore and use grunt-bowercopy[0] to move the files you actually want from bower_components/ to public/{js,css} or wherever. Files get committed once they're in public/ and I only re-run the grunt task when I want to upgrade a lib. I can understand people thinking this is overkill for a small project, but when you have dozens of libraries it's nice to have dependencies and their versions clearly defined. [0]: https://www.npmjs.com/package/grunt-bowercopy https://www.npmjs.com/package/grunt-bowercopy

by xrstf 12y ago

krapp 12y ago

> If you know a better way to install grunt-contribs, please tell me. I would just not use grunt. I understand it's not required to run it, but even as a build dependency, unless you already have Node installed and running, it's a lot of overhead for relatively little benefit, I think.

arenaninja 12y ago
I'm on the fence on this one. On one hand, I'm fond of package managers. On the other, there's a TON of crap every time I run bower install... I've yet to figure out the best way of doing things. I'm thinking of using bower-installer, ship with a copy of the assets, and include bower.json, but not bower_components/. The other alternative is obviously CDNs, but then you're maintaining assets manually
- krapp 12y ago
  PHP already has a package manager though (Composer.) Granted, the amount of friction involved depends on personal preference, and whatever environment you're working in, but why require a package manager in another language (and, potentially, the language itself) when one exists for the language you're actually deploying in?
  - girvo 12y ago
    I'm sympathetic to your point. Where I work, we use Grunt and npm for our PHP projects, and I'm in the process of replacing them (slowly but surely) with PHP-based versions of the tools we use, and replacing Gruntfiles with Makefiles. It's experimental, currently, but I feel like it's doable. The only dependency then is PHP and Composer, which I think is nice.
- bombtrack 12y ago
  I include bower_components/ in .gitignore and use grunt-bowercopy[0] to move the files you actually want from bower_components/ to public/{js,css} or wherever. Files get committed once they're in public/ and I only re-run the grunt task when I want to upgrade a lib. I can understand people thinking this is overkill for a small project, but when you have dozens of libraries it's nice to have dependencies and their versions clearly defined. [0]: https://www.npmjs.com/package/grunt-bowercopy https://www.npmjs.com/package/grunt-bowercopy