how to build

[yanmeng26]

Hi,
I am interested in this project and I want to learn more to see if I can contribute to some issues.
can you explain how to build it ? since there is no instruction about building in readme.md

[evanharmon1]

Hello. Glad to hear you are interested in helping out. Check out the backend repo for instructions on how to build the backend part at https://github.com/codeforkansascity/meep-backend

…

On May 20, 2019, 3:41 PM -0500, yanmeng26 ***@***.***>, wrote: Hi, I am interested in this project and I want to learn more to see if I can contribute to some issues. can you explain how to build it ? since there is no instruction about building in readme.md — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[yanmeng26]

Hi, how about front end build up?
so meet is only just for front end and the meet-backend is for back-end, right ?

[galbwe]

@yanmeng26 Yes that is correct. To run the frontend, make sure you have npm installed. Move to the frontend directory and do npm install, then npm run dev-server. Go to localhost:8080 in a browser and you should see the app running.

Please feel free to reach out if you have any questions.

[clementkng]

@evanharmon1 @galbwe Are there any specific instructions in the backend build regarding running this project on WSL on Windows 10? When I attempt to instructions under the docker section, I get stuck after the docker run -p 8001:8000 meep-backend:gunicorn step and localhost does not connect.

[galbwe]

@clementkng I don't think anyone has tried it using WSL yet, so there is no specific documentation for that.

To clarify, is the problem that the container is running when you try to connect, but not responding, or is it that the app crashes and the container is destroyed when you try to run it?

When running the app from windows 10 using powershell in admin mode, we've found that sometimes you need to restart docker before it will work, as discussed in this thread. Not sure if it applies here, but it can't hurt to try.

Let us know if you still can't get up and running and we can try to figure something out.

[clementkng]

@galbwe Thanks for responding!

I believe the container is running, but it isn't responding. When running from Powershell in admin mode, running docker container ls from another window shows that the container is up, but localhost is still refusing to connect. Running docker restart with the container name also has no effect.

[galbwe]

@clementkng Okay. Try doing docker logs <your container name>. What output do you get?

[clementkng]

@galbwe I realized that docker run hello-world was not working, so I suspect something is fundamentally wrong w/ my docker setup. I'll try resolving my setup for now and will come back to this if I get similar errors. Thanks for all your help!

[galbwe]

@clementkng It could be something like running linux containers vs. windows containers. Also see here. Their error looked similar to yours.

Good luck!

[clementkng]

@galbwe I was able to reinstall docker, verify that the backend works, and got to the sequence of instructions to build out the frontend. In the meep directory, I run npm init, then npm install, but when I run npm run dev-server I get an npm error saying that I have a missing script: dev-server.

I've tried installing the dev-server package and tinkering w/ the package.json, but haven't had any luck on being able to run this command successfully. Is there a step I missed somewhere?

[galbwe]

@clementkng I updated the readme with installation instructions. Let us know if that works. You might want to do a git pull first to grab an import fix I just made.

[clementkng]

@galbwe Thanks very much, I have a local build working now!

[galbwe]

@clementkng You are welcome. If you have any questions about project structure (or lack thereof), don't hesitate to ask.

[Spechal]

Instructions included in #55 and #67

[krisstee]

Closed since this seems to be resolved. Pinned issue for future reference.