don/www.duckland.org
1
0
Fork 0
Code Issues Pull requests Releases Activity

first hugo commit

Browse source
This commit is contained in:
Don Harper 2019-05-26 18:26:26 -05:00
parent dabdd68df3
commit 0e4f2a913d
1459 changed files with 50871 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
content/post/2017/11/really-moving-in-on-the-chromebook.md Normal file
View file

@ -0,0 +1,19 @@
+++
date = "2017-11-13T00:03:15-07:00"
title = "Really moving in on the Chromebook"
slug = "really-moving-in-on-the-chromebook"
+++
As I <a href="https://www.duckland.org/2017/08/welcome-to-the-new-look/" target="_blank" rel="noopener">mentioned a while back</a> that I was experimenting with using a Chromebook, I decide to see how far I could take it.  On <a href="https://www.duckland.org/2017/09/back-from-london-again/" target="_blank" rel="noopener">my recent trip to the UK</a>, I only took my Acer C720 with me.  During the trip, I used it for things like uploading photos I took, Skype to chat with the family, checking email and news, and remote access while in the hotel room.
This worked out pretty well, to the point where I am trying to use it or my HP Chromebook 11 G1 full time.  While I can get lots of things done in a browser now days, there are some things I find my self sshing back to another box to do.  So, I decided to see if I could do that on the Chromebooks.
The &#8216;normal&#8217; way is to install Linux into a chroot using something call <a href="https://www.linux.com/learn/how-easily-install-ubuntu-chromebook-crouton" target="_blank" rel="noopener">Courton. </a>I have done that in the past, but the work flow is not something I can adapt to easily as it involves more than a simple key combo to switch between.
I found a project called &#8220;<a href="https://github.com/skycocker/chromebrew" target="_blank" rel="noopener">Chromebrew</a>&#8221; in the vein of &#8220;Homebrew&#8221; for MacOS.  Setup is pretty simple as I had turned on Developers mode on my boxes a long time ago, so it was a matter of downloading a script, reading it, and then running it.
From there, I used the **crew** command to install some basic tools (git, vim, & python), and I can now do 90% or more of my day-to-day work on the Chromebooks.
The only thing that I have not figured out yet is a decent VPN solution, but I am working on that.
I suppose at some point, I will upgrade one of the Chromebooks to one of the newer generation which can run Android apps as well.