Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Posted by William J. Terrell
William J. Terrell
17,403 Points

Console, Node, and Git?

Going through some of the courses on here, there are still some technologies that I am...perhaps finding the concepts elusive.

I was hired on as a web-developer about a year ago and we're using a CMS called Cascade Server to build our site and publish it to the server...

I guess I just don't really see where the Console would come into play here? Maybe some of the base concepts are escaping me? Could anyone offer some insight?

Thanks!

1 Answer

Jay Wellings
Jay Wellings
4,593 Points
Jay Wellings
Jay Wellings
4,593 Points

I'm not familiar with Cascade Server, but if you are using a CMS, you are probably using a web front end to interact and manage your application.

The benefit of this is the creators of the CMS have abstracted many of the processes involved in maintaining a application in a easy to use front end.

In your workflow it sounds like you dont need to use Console / Git / Node as this is all handeled by the CMS. However if you were to move to another company / do side projects that did not use these CMS tools like these would helpful, and are used in many development houses.

Part of the value of using Console is that you are the one performing these actions, not the CMS, as such you then get a deeper understanding of the mechanics of what is going on.

Hope that helps.

William J. Terrell
William J. Terrell
17,403 Points

Thanks for the additional insight :) I guess the way I see it is, "back in the day", interacting with the command line was the best that the technology of the time would allow, correct? The GUI (the "Desktop", "Environment", "Folders", etc.) came along later.

I guess what I'm trying to see is the benefit of working from the command line. To me, operating at that level is infinitely more abstract.

I don't know if it's accurate, but the analogy I come up with is trying to drive the car from under the hood instead of in the driver's seat...

William J. Terrell
William J. Terrell
17,403 Points

I've started the Console Foundations course over again, and I think I get at least part of the concept now. According to Jim Hoskins:

"Websites and web applications will be deployed on remote computers called servers, and most of the time, the only way to interact directly with these machines is to use a command line over a remote connection called SSH."

So, I guess the system we have set up here has three sides:

1.) My office: the CMS

2.) My Neighbor's Office: the "back-end" (databases and the like, which I will also be getting into soon :) )

3.) The Guys Downstairs: the Server Room (which I do some small things on the server from time to time, but they are mostly 301 redirects, which I use IIS to set up)

But, if I wanted to learn more "server stuff", or if I moved to another company later on that wanted me to do more on the server-side of things, I would need to know the Console, right?

Either way, if I can get it down, it'll just be one more thing in my repertoire. There's no such thing as having too many skills, right? :)

All that being said, I guess what I should really be learning is PowerShell, right?