karlstolley / 535

Course materials for COM535: Instructional Design
http://karlstolley.github.com/535/
1 stars 6 forks source link

Viewing my updated page live #43

Closed kchughes closed 11 years ago

kchughes commented 11 years ago

Okay, so I don't know if I missing something (wouldn't be surprised) or if I'm just doing it wrong (still wouldn't be surprised). I've tried it several ways but I keep getting the same result. In my terminal I run jekyll and I'm able to view the page at http://localhost:4000/html/, however, I can only see old content, which happens to be the content from when the last pull request was approved. I've pushed, pulled, and rebased, and still nothing. I just want to make sure my structure and css changes are rendering correctly.

Will I not be able to see my updated pages live anymore (as in on the internet) now that we've moved over to using yaml? Will I not be able to see anything until the pull requests go through?

How does everybody else see their latest content live?

If anybody has any ideas I would greatly appreciate you sharing them.

ghost commented 11 years ago

Hi Khalila-

The only thing that comes to mind is that maybe you're looking at the wrong branch of your repository. Make sure you're in the directory that holds the kchughes version of the 535 project, then checkout the dev branch. If you type "git log -5" you should see a list stating the most recent changes you made. Then if you run "jekyll --server --auto" from the same directory, you should see your new code at localhost.

You should also make sure your browser's cache is cleared out--I've noticed that Chrome and FireFox sometimes have to be forced to reload old files by removing them from the cache.

Christine

On Sat, Nov 24, 2012 at 10:41 PM, kchughes notifications@github.com wrote:

Okay, so I don't know if I missing something (wouldn't be surprised) or if I'm just doing it wrong. I've tried it several ways but I keep getting the same result. In my terminal I run jekyll and I'm able to view the page at http://localhost:4000/html/, however, I can only see old content, which happens to be the content from when the last pull request was approved. I've pushed, pulled, and rebased, and still nothing. I just want to make sure my structure and css changes are going rendering correctly.

Will I not be able to see my updated pages live anymore (as in on the internet) now that we've move over to using yaml? Will I not be able to see anything until the pull requests go through?

How does everybody else see their latest content live?

If anybody has any ideas I would greatly appreciate you sharing them.

— Reply to this email directly or view it on GitHubhttps://github.com/karlstolley/535/issues/43.

kchughes commented 11 years ago

Thanks Christine. I tried doing what you suggested but got the same result. I am on the right branch. I also looked at it with another browser and this one (safari), interestingly enough, loaded the same pages but did not load the yaml.

I played around with it a little more and found that the pages that were being loaded are the ones in the _site folder. I think this is supposed to happen (?). But what is not happening is my updated pages in the html folder is not getting updated from my dev branch (or however you say it) html. Basically, the pages in the _site folder are the ones from when the last pull request was approved. But my latest pages are in my html folder (535/html) and the 535/_site/html folder is not being updated. So I guess my question now is - how do I update the _site folder? I am pretty sure that I'm not supposed to be doing this manually. Another question might be, if I can't updated the _site folder, how can I view my html folder only?

ghost commented 11 years ago

I'm stumped. You'll have to wait for Karl to sort it out. I do know that the _site folder is updated automatically, so you don't make any changes there. If you have all your changes stored github, maybe try re-cloning your repo in another location?

On Sun, Nov 25, 2012 at 4:28 PM, kchughes notifications@github.com wrote:

Thanks Christine. I tried doing what you suggested but got the same result. I am on the right branch. I also looked at it with another browser and this one (safari), interestingly enough, loaded the same pages but did not load the yaml.

I played around with it a little more and found that the pages that were being loaded are the ones in the _site folder. I think this is supposed to happen (?). But what is not happening is my updated pages in the html folder is not getting updated from my dev branch (or however you say it) html. Basically, the pages in the _site folder are the ones from when the last pull request was approved. But my latest pages are in my html folder (535/html) and the 535/_site/html folder is not being updated. So I guess my question now is - how do I update the _site folder? I am pretty sure that I'm not supposed to be doing this manually. Another question might be, if I can't updated the _site folder, how can I view my html folder only?

— Reply to this email directly or view it on GitHubhttps://github.com/karlstolley/535/issues/43#issuecomment-10699568.

karlstolley commented 11 years ago

Make sure that you're not running another Jekyll instance somewhere. Try killing the Jekyll process (Ctrl C in your terminal window), and try hitting the http://localhost:4000/ URL again -- if you think you killed Jekyll but you're still seeing a page loading up at that URL, run this in your command line:

  $ ps aux | grep jekyll

If Jekyll is running, the command line will return something like

  username         8791   0.0  0.4  2490192  34284 s000  S+   10:33AM   0:00.49 /Users/username/.rvm/gems/ruby-1.9.3-p194/bin/jekyll  

Note the number following username (in this case, 8791--that's known as its process ID, or PID). If you have more than one instance of Jekyll running, there may be more than just one number.

With that number or numbers, you can stop all of the Jekyll processes by running kill followed by the PID:

  $ kill 8791

Once you've killed all of the Jekyll PIDs, try again hitting http://localhost:4000/ -- you should get some kind of "Could not connect..." error in your browser.

Hope that helps.

kchughes commented 11 years ago

It worked! Thank you!