builds fine, can't reach build/index.html about angular-wordpress-seed

[michaelbromley]

Hi,

First of all, what do you mean by "can't find it" - 404 error? Any message in the console?

Have you looked at the built index.html file? All look normal?

Do you have mod_rewrite enabled on your apache install? It's required by the html5mode urls.

The port should not matter, just whatever port you serve http over.

[linkingarts]

I can run other angular apps no problem. It's not a 404, it's one of those
"browser can't find apex so it tries the www" things. So I try
http://sites.local/.../build and it times out, then tries
http://www.sites.local/.../build which of course just times out.

I've tried editing the file already, re-installing a fresh copy of your
repo.

Seems like maybe there's a permissions thing somewhere, and that it's
probably my setup somehow, though what I don't understand is why I can
build other angular apps no problem.

Is gulp watch running on :80?

thanks for the (quick!) response

On Mon, Aug 24, 2015 at 2:19 AM, Michael Bromley [email protected]
wrote:

Hi,

First of all, what do you mean by "can't find it" - 404 error? Any message
in the console?

Have you looked at the built index.html file? All look normal?

Do you have mod_rewrite enabled on your apache install? It's required by
the html5mode urls.

The port should not matter, just whatever port you serve http over.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

Peter Jacobson
Linking Arts
www.linkingarts.com
www.wedocracy.com
www.petejacobson.com
twitter.com/petejacobson
twitter.com/linkingarts
[phone] / VoIP
[phone] / mobile
peterjacobson / Skype

people + technology + art

[michaelbromley]

I think by default livereload (part of the watch task) runs on port 35729. Sorry I can't help further. If you figure it out, please note the solution here in case anyone else runs into it.

[linkingarts]

Will do, thx

On Tue, Aug 25, 2015 at 1:12 AM, Michael Bromley [email protected]
wrote:

I think by default livereload (part of the watch task) runs on port 35729.
Sorry I can't help further. If you figure it out, please note the solution
here in case anyone else runs into it.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

Peter Jacobson
Linking Arts
www.linkingarts.com
www.wedocracy.com
www.petejacobson.com
twitter.com/petejacobson
twitter.com/linkingarts
[phone] / VoIP
[phone] / mobile
peterjacobson / Skype

people + technology + art

[cristiam86]

@linkingarts I finally solved this problem. After commenting/deleting the .htaccess sections that does it, you have to clean your Google Chrome's cache.
I figured it out when, without doing nothing, I opened the same link on another browser and it worked.

[linkingarts]

ok will test, thx u

On Thu, Oct 1, 2015 at 5:08 AM, cristiam86 [email protected] wrote:

@linkingarts https://github.com/linkingarts I finally solved this
problem. After commenting/deleting the .htaccess sections that does it, you
have to clean your Google Chrome's cache.
I figured it out when, without doing nothing, I opened the same link on
another browser and it worked.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

Peter Jacobson
Linking Arts
www.linkingarts.com
www.wedocracy.com
www.petejacobson.com
twitter.com/petejacobson
twitter.com/linkingarts
[phone] / VoIP
[phone] / mobile
peterjacobson / Skype

people + technology + art