orientation / orientation Goto Github PK

Codez involving current_user are difficult to test without the ability to log in. Is it possible to get our auth system working in development?

Duh. Who's going to work on updating articles on Caturday?

Thanks for the suggestion @adamfortuna. 👍

Like a github issue

I know for a fact Arron didn't update this in January:

Oddly enough fresh? returned true which means internally the updated_at isn't January 3rd, so that must be a view bug.

It was exposed in the repo. Should only be in the Heroku env vars.

It's kind of dumb to hotlink.

Either by using a simple edit log or by going all out and switching to Gollum (https://github.com/gollum/gollum) to store the articles using Git

Can't figure that one out.

http://orientation.codeschool.com/authors

Any ideas @drewbarontini?

I think we may have more success with orientation as browsable documentation rather than keeping it search-centric. This may be as simple as a styling change.

So, perhaps try moving the ToC-like thing on the right over to the larger column in the left, and show every article (rather than cutting off the list). Then move search over to the right.

Could also take the time to categorize everything, though better to test the thought before we put lots of work into it. :)

@olivierlacan we discussed how to fix this, apparently you said that simple_form is causing this.

It logs out users far too often because of token expiration issues.

1. Go to an article
2. Hit Edit
3. Select text
4. Hit the Tab key
5. You'll find your cursor way to far along the line.

Would be useful to switch old articles by people who left the team to new "maintainers".

Cool suggestion by @askbill.

They were exposed in the repo, silly me.

Hey @thomas, can you make sure to update the info to access course apps, it's crucial when doing debugging and support: http://orientation.codeschool.com/articles/accessing-production-course-applications

@adamfortuna already added info about Rails 4: Zombie Outlaws but the courses you already move need to be updated too, and if you have any notes, feel free to edit the document.

Example: deploy process after we migrated from Heroku to BlueBox

One of the main purposes for this page is to let people know who's who. That's a little hard to do with such small pictures. Any chance we could try to bump the size a bit? 😃

http://orientation.codeschool.com/authors

To let people who've been notified about a potentially stale article declare it so fresh and so clean if it indeed is.

It would be nice to archive articles instead of deleting them altogether.

I think I'm hesitant to delete articles because they still contain helpful tidbits even if they're stale.

For example, this article on Adding Student Discounts is super simple. And this old version probably doesn't need to be there.

But it's still worth keeping an archive of old articles to see how things used to work. Another example is that most courses are running on BlueBox now, but the stale Heroku articles still have practical applications to both Try Ruby and Try Git.

Github authentication that allows anyone in who is part of the codeschool team would awesome for al our tools. Might even be a good way to determine admin status on codeschool as well.

See: http://orientation.codeschool.com/articles/complete-all-exercises-on-a-course-for-user/edit

When you click "Mark Fresh" nothing happens.

/cc @aimeesimone

Positive reinforcement FTW.

This has been happening for as long as I can remember. I probably screwed something up somewhere.

Exit timeout: Heroku/codeschool-orientation 

2013-10-10 18:10:08.436 
188 <45>1 2013-10-10T18:10:08.368414+00:00 heroku web.1 - - Error R12 (Exit timeout) -> At least one process failed to exit within 10 seconds of SIGTERM 

Go to the log: https://api.heroku.com/myapps/[email protected]/addons/logentries 

You are receiving this email because your Logentries alarm "Exit timeout" 
has been triggered. 

In context: 
2013-10-10 18:10:02.856 187 <13>1 2013-10-10T18:10:02.683864+00:00 app web.1 - - I, [2013-10-10T18:01:54.254085 #2] INFO -- : Completed 302 Found in 1ms (ActiveRecord: 0.0ms) 
2013-10-10 18:10:02.877 207 <13>1 2013-10-10T18:10:02.683864+00:00 app web.1 - - I, [2013-10-10T18:06:54.320438 #2] INFO -- : Started GET "/login" for 108.62.115.226 at 2013-10-10 18:06:54 +0000 
2013-10-10 18:10:02.877 183 <13>1 2013-10-10T18:10:02.683864+00:00 app web.1 - - I, [2013-10-10T18:06:54.322552 #2] INFO -- : Processing by SessionsController#new as HTML 
2013-10-10 18:10:02.877 255 <13>1 2013-10-10T18:10:02.683864+00:00 app web.1 - - I, [2013-10-10T18:06:54.324425 #2] INFO -- : Redirected to http://orientation.codeschool.com/auth/google_oauth2?origin=http%3A%2F%2Forientation.codeschool.com%2F 
2013-10-10 18:10:02.877 187 <13>1 2013-10-10T18:10:02.683864+00:00 app web.1 - - I, [2013-10-10T18:06:54.324896 #2] INFO -- : Completed 302 Found in 2ms (ActiveRecord: 0.0ms) 
2013-10-10 18:10:02.877 100 <13>1 2013-10-10T18:10:02.683864+00:00 app web.1 - - Exiting 
2013-10-10 18:10:06.718 108 <13>1 2013-10-10T18:10:06.642627+00:00 app web.2 - - => Booting Thin 
2013-10-10 18:10:06.816 165 <13>1 2013-10-10T18:10:06.642627+00:00 app web.2 - - => Rails 4.0.0 application starting in production on http://0.0.0.0:9887 
2013-10-10 18:10:06.816 142 <13>1 2013-10-10T18:10:06.642627+00:00 app web.2 - - => Run `rails server -h` for more startup options 
2013-10-10 18:10:06.816 121 <13>1 2013-10-10T18:10:06.642627+00:00 app web.2 - - => Ctrl-C to shutdown server 
2013-10-10 18:10:08.436 188 <45>1 2013-10-10T18:10:08.368414+00:00 heroku web.1 - - Error R12 (Exit timeout) -> At least one process failed to exit within 10 seconds of SIGTERM 

Orientation is sending multiple emails with the same article listed. My hypothesis is that it's looping through the correct number of stale articles, but only grabbing the first one and sending a separate email for each of them.

Here's how I see that working:

Orientation.configuration do |config|
  featured_tags: ["courses", "support"]
end

It would sort of make sense to send of list of links to all the stale articles if there are more than one instead of sending an email per article.

It'd be nice if orientation kept track of article changes and also had a feed of diff's so we can see what has been recently changed.

Gotta let people search right away within having to click around.

Stale is automatic and a guess (based on time), rotten is factual and based on reader feedback.

Like billing and devops.

Either that or we should switch to using GitHub's organization OAuth as a solution: http://stackoverflow.com/questions/12792326/how-do-i-refresh-my-google-oauth2-access-token-using-my-refresh-token

The problem is that everybody has access to Google Apps and an @envylabs.com address, not everybody has GitHub.

Maybe Basecamp would be an alternative too.

Bit of a bummer.

Currently if the JS breaks we submit an empty input field for tags and it wipes out all the article's tags. Dat's bad.

http://orientation.codeschool.com/articles/restart-a-course-app

Doesn't attempt to load any tags when typing.

@olivierlacan was kind enough to set up orientation-staging on Heroku.

A few other things that would be Super Awesome:

• Configuring Bugsnag to report only production errors (or creating a separate Bugsnag whatnot for staging errors)
• Configuring Mandrill to send mail in the staging environment

These are mostly notes to self for now. I may end up adding to this issue or deleting it entirely.

It'd be nice to allow for an option to not receive emails from Orientation. I'd like "Some of your Orientation articles might be stale". For now I just have a filter to skip inbox/archive for these emails, but if people want to have this and stay up to date on them, it'd be nice to be able to enable/disable this depending on if the person has time to update articles.

We need to say when no results are available when searching otherwise it leaves a weird feeling that maybe search doesn't work right.