search

S1SYPHOS / Vagrant-Kirby-Starter-Kit

Getting started with Vagrant & Kirby v3 in no-time
MIT License
1 stars 0 forks source link

running npm start #1

Open grommas opened 3 years ago

grommas commented 3 years ago

Hi Martin,

I'm fooling around with this starter kit. Is it necessary to run npm start inside or outside the VM? When starting outside, everything seems to run only over the IP address, no luck with localhost and browsersync does not refresh the content.

Tried to use the more secure setup as well but ended up with an 404 error of 127.0.0.1:50432 [404]: / - No such file or directory.

Do I have to set a new localURL or need to change anything else to get it working?

All the best, Jakob

S1SYPHOS commented 3 years ago

Hey there, the VM is running under 192.168.69.69 by default, starting it with the command mentioned should start a proxy with live reload, which in turn is accessible under localhost:3000 (or was it 4000?).

.. but I get the feeling that doesn't answer your question ;)

grommas commented 3 years ago

I'm not sure, since it seems not working like that for me. Maybe I do something wrong. I have to start the VM server with vagrant up, and then run cd htdocs && npm start, right? Do I have to replace the Apache .htaccess from your Gulp-Kirby-Starter-Kit with the nginx equivalent?

S1SYPHOS commented 3 years ago

I'll check it out and report back ;)