Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@SpaceK33z
Copy link
Member

I documented how you can use webpack-dev-server with Vagrant.

I know it may be not the most important aspect, seeing how much still needs to be done, but I also wanted to get some practice with documenting a how-to. There will be more!

The part I'm not sure about is whether to show a full working Vagrantfile. At the moment I show only one config thingy from the Vagrantfile.

Related: #26

Sidenote: the contributing guidelines say to create an issue first when creating a new page, but this was already discussed in #26. Is this good enough?

@SpaceK33z SpaceK33z mentioned this pull request Aug 27, 2016

The server should be accessible on `http://10.10.10.61:8080` now! If you make a change in `app.js`, it should live reload.

## Advanced usage with nginx
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Convert to title case (Advanced Usage with nginx).

@SpaceK33z
Copy link
Member Author

@bebraw, thanks, implemented your feedback!

@bebraw bebraw merged commit dc8ebf5 into webpack:develop Aug 28, 2016
@bebraw
Copy link
Contributor

bebraw commented Aug 28, 2016

Merged. Thanks.

@SpaceK33z SpaceK33z deleted the feature/add-develop-using-vagrant-page branch August 28, 2016 09:43
sallar pushed a commit to sallar/webpack.js.org that referenced this pull request Oct 19, 2016
…g-vagrant-page

Documentation for how to develop using Vagrant
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants