Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up instructions #60

Closed
ugogo opened this issue Jan 16, 2018 · 6 comments
Closed

Set up instructions #60

ugogo opened this issue Jan 16, 2018 · 6 comments

Comments

@ugogo
Copy link

ugogo commented Jan 16, 2018

Hey guys,
I was trying to set up locally Jarvis, but I ran into two issues

There are two servers launched in parallel, is this wanted?
localhost:3000 and localhost:1337
https://www.dropbox.com/s/5l7j90ttjhug4ao/Capture%20d%27%C3%A9cran%202018-01-16%2010.28.41.png?dl=0

The "dev" one seems to be on :3000, but it seems broken:

  • Missing CSS file
  • Lot of NaN
  • No bundles listed

https://www.dropbox.com/s/g2j0a1ch2hptwo7/Capture%20d%27%C3%A9cran%202018-01-16%2010.29.55.png?dl=0

Steps to reproduce:

  • git clone ...
  • npm install
  • npm run dev

Am I missing something?
Thanks!

@Sunshine168
Copy link
Contributor

Sunshine168 commented Jan 16, 2018

oh it seem jarvis break in it's dev mode .
because#33 custom port support

if you change document.location.port to 1337 it will work ,just access localhost:1337. And we can discuss a better way to fix it ,

localhost:3000 is the dev server for develop jarvis as a developer
localhost:1337 is for you to use jarvis as a user

hope to help you ~

Sunshine168 added a commit to Sunshine168/jarvis that referenced this issue Jan 16, 2018
@zouhir
Copy link
Owner

zouhir commented Jan 16, 2018

Investigating... please give me little time ⏳🙀

@ugogo
Copy link
Author

ugogo commented Jan 31, 2018

Any updates guys? 😢

@stephencookdev
Copy link
Contributor

This can be closed, right? Looks like this has been fixed by e972f44 and aa32fd9 (same as #104)

Just running npm run watch seems to work fine, now

@lukeed
Copy link
Collaborator

lukeed commented Feb 22, 2018

Yes, #112 completely changed & simplified the development process. It's now all under a single server~!

@lukeed lukeed closed this as completed Feb 22, 2018
@ugogo
Copy link
Author

ugogo commented Feb 22, 2018

Yep, I can confirm that everything is working as expected now, thx guys

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants