-
Notifications
You must be signed in to change notification settings - Fork 863
Question on Gruntfile.js Line 200 #575
Comments
I think the line numbers are wrong, look for this block of code browserSync: {
dev: {
bsFiles: {
src : [
'assets/stylesheets/*.css',
'**/*.php',
'assets/javascript/**/*.js'
]
},
options: {
watchTask: true,
// fill in proxy address of local WP server
proxy: ""
}
}
} the proxy server is what you want to change under options. For my WordPress site I simply just put in site.dev. I'm running AMPPS for my server. |
That's what I was thinking too about the line numbers being wrong. Definitely going to add my local dev to the proxy key. On a side note, I also found adding my local dev to grunt.registerTask('default', ['http://local.dev/','watch']); I'm using my Mac's native stack w/ |
The line # has changed over time since Browsersync was first implemented and the README needs an update to reflect that. @LukePettway has pointed out the correct location to place the URL. |
We just switched from Grunt to Gulp. This will be the correct place to add your local dev URL: |
I know I probably sound like an idiot but when viewing Gruntfile.js, this is all I see from lines 198-200:
The instructions say we are to add our local WP-Server address to line 200. The only line where there's any indication of adding URL or any kind is at Line 180 for the
proxy
value. Shouldn't that be where we add the address of our local WP-Server -- Line 180?I just want clarification as I'm confused by the instructions given.
The text was updated successfully, but these errors were encountered: