Discuss This Topic
There are 1 comments in this discussion.
Read and join this discussion
Topic: Getting Brunch to work under POW rather than localhost:3333
Topic type:
Quick post on the steps necessary to use a virtual hostname rather than localhost and port number via POW even when using Brunch.
I'm using ember-brunch as my build toolkit for a Ember.js project I'm working on. It's built on top of Brunch and I'm enjoying it so far.
However, one thing that bugged me was that the included server was only accessible at localhost:3333 when running in development. Ugly, for a POW user like myself. There had to be a way to make it work under a virtual hostname.
Turns out there is a very simple way of doing it in POW since 0.4.0 as outlined here:
http://pow.cx/manual#section_2.1.4
Basically create a file with the port number in it under ~/.pow where the filename is the virtual hostname you want, but minus the ".dev". Then you, once you start up the server with "brunch w --server", you can access your project with "filename.dev" in the browser.
The hardest part of this was searching for the answer!
Walter McGinnis
said Update: Working with ember-cli
I'm working with ember-cli now rather than brunch. The same technique works.
That is create a file under ~/.pow/ named for you app and containing only the port number. In ember-cli's case this is 4200 by default.
You can use the powder gem's executable to do this:
Tags: ember-cli, Ember.js, port proxying, pow, web server