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

cannot see api_server.py #66

Open
snaqviApps opened this issue Jun 3, 2017 · 4 comments
Open

cannot see api_server.py #66

snaqviApps opened this issue Jun 3, 2017 · 4 comments

Comments

@snaqviApps
Copy link

Hi

I am relatively newer to this HTTP server config. (if right phrase to start with), however was able to get to the step

  • vagrant ssh
    however I don't see anywhere "api_server.py" file so could carry out the Lesson2:5th section (Sending API Requests),

Could someone guide me along,

thanks

Steps carried out so far (apart from some good troubleshooting :) )

...........

  1. git clone http://github.com/udacity/fullstack-nanodegree-vm fullstack
  2. cd fullstack/vagrant
  3. vagrant up
  4. vagrant ssh
  5. ls
    Inside ALL I see:
  • API (directory that I created 'manually' after comming in SSH)
  • fullstack (directory)
  • redis-stable (directory)
  • redis-stable.tar.gz

NO "api_server.py" file

@twhetzel
Copy link

twhetzel commented Jun 3, 2017

@snaqviAndroidApp can you post your question to the Full Stack Nanodegree forums?

@snaqviApps
Copy link
Author

@twhetzel Can you share one such link

@pkshreeman
Copy link

@snaqviAndroidApp

The forum that @twhetzel is referring to start at this link: https://discussions.udacity.com/ and you might want to go to the specific group on drop-down menu in relation to what course you are taking. By the way, I believe once you do vagrant ssh, you need to cd /vagrant to see these folders and files.

@twhetzel
Copy link

twhetzel commented Jun 3, 2017

Yes, that's correct on both responses

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

No branches or pull requests

3 participants