treehouses / treehouses.github.io

A Markdown Wiki for treehouses 🏡

Welcome to treehouses

What is treehouses?

treehouses is the name of our system allowing us to share our different learning platforms via the Raspberry Pi series of single-board computer devices.

Currently the Raspberry Pi models supported are: the zero W, the Pi 3, the Pi 3B+ and the Pi 4

Main system branches

treehouses consists of several parts:

cli

We have created our suite of commands to be used in the Raspberry Pi terminal, which can be found in treehouses/cli

npm i @treehouses/cli

builder

This is where our modified Raspberry Pi images are created: treehouses/builder.

remote

Currently in remote, we are developing an Android app which allows Android phones and tablets interact with the terminal of the Raspberry Pi over Bluetooth: treehouses/remote.

treehouses.github.io's Issues

step9: rate treehouses remote on play store before changing to beta mode

I suggest that we add this either in the body of Step 9, or at the top of orientation.md

create chat like in ole.gh.io but

... to https://gitter.im/treehouses/Lobby

first steps sidebar titles

Will need to change step titles to second level header

Unknown public keys in ~/.ssh/authorized_keys file

On executing below command, I see few unknown keys under .ssh/authorized_keys file.
sudo treehouses sshkey add "your SSH key"

virtual intern navbar needs dropdown

"virtual interns" tab in navbar needs dropdown like in OLE

Redirecting issue maybe?

Clicking on treehouses.io first redirects to Page not found and then to welcome page.

trackprogress.md required

trackprogress.md from OLE needs to be added in pages/vi

new blog structure

move existing blogs to new directory

pages/blog/blog.md

each blog should get its own folder based on date eg. pages/blog/20190816/

Host key verification failed error

This is error is prompted during the ssh login attempt after the RSP4 booted with a new tree houses image. I was using PC as ssh client.

User won't be able to login to the RP4. The following command will fail to execute
ssh -v [email protected]

Change for SSH Tutorial

To add your SSH key to your Raspberry Pi, run: treehouses sshkey add "your SSH key" (copy-paste your SSH key in between the quotes).

https://treehouses.io/#!pages/vi/sshpi.md
before running this command, users need root privilege to append keys.

Make image path relative

Image path needs to be relative as it does not show up on raw.githack link

explain which kind of commands work in treehouses remote

In Step 1 , section 2:
No Response from android treehouses remote app when trying to execute commands.

add check if sshkeys are in the right place

when following Step 2 and trying to ssh root@[local ip] into my raspberry pi I am asked for a password. Not sure what the password is as the guide does not say. (raspberry did not work as the password for ssh root@[local ip] but does work for ssh pi@[local pi])

pihole blog post

move old blogs to right directory structure

switch color scheme to white on black

http://dynalon.github.io/mdwiki/#!index.md
has a change theme thing ... Cyborg is white font on black background

Picture missing to demo tor + nextcloud + docker

Looking at https://treehouses.io/#!pages/vi/nextcloud-tor.md
Picture links are missing.

treehouses remote testing link vs production

https://play.google.com/apps/testing/io.treehouses.remote
-> testing

https://play.google.com/store/apps/details?id=io.treehouses.remote
-> production

we want VI to use testing version

Create faq page in pages/vi

Add "#Helpful_Links" from https://open-learning-exchange.github.io/#!./pages/vi/vi-faq.md#Helpful_Links

Redundancy typo in "list.md"

The line in github.io/pages/blog/list.md:

treehouses.io in DevOpsDay Jakarta 2018 on May 5, 2018 by empeje

should be:

treehouses.io in DevOpsDay Jakarta on May 5, 2018 by empeje

Possible content add for git checkout

https://treehouses.io/#!./pages/vi/github-issues.md Looking at create a new branch section. The instruction is clear as glass.

But, as a person who works on two or more PRs before the approval of the merging, I always forget to switch back to master branch before creating a new branch.
I suggest that we add the git checkout -b <new_branch_for_PR> master command in the tutorial. It will prevent us from branching from a current working branch. Then, we can freely switch branches by git checkout <branche_name> and work on our commit.

new README.md

finish firststeps step1

remove old docs and download

git checkout master command error

Using git bash, users may be unable to change the branch.

git checkout master
error: pathspec 'master' did not match any file(s) known to git
hint: 'master' matched more than one remote tracking branch.
hint: We found 2 remotes with a reference that matched. So we fell back
hint: on trying to resolve the argument as a path, but failed there too!
hint:
hint: If you meant to check out a remote tracking branch on, e.g. 'origin',
hint: you can do so by fully qualifying the name with the --track option:
hint:
hint:     git checkout --track origin/<name>
hint:
hint: If you'd like to always have checkouts of an ambiguous <name> prefer
hint: one remote, e.g. the 'origin' remote, consider setting
hint: checkout.defaultRemote=origin in your config.

While following the repository guide, https://treehouses.io/#!pages/vi/gitrepositories.md, I encounter issue above. As changing branches was meant to be applied on my remote repo which is a fork version of the treehouses, but git seems to fail to change the branch.

$ git checkout
Your branch is up to date with 'origin/create-branch-treehouse_fork'

Also, here is the proof that I name the repo correctly.

git remote -v
origin  https://github.com/phamduchongan93/phamduchongan93.github.io.git (fetch)
origin  https://github.com/phamduchongan93/phamduchongan93.github.io.git (push)
upstream        https://github.com/treehouses/treehouses.github.io.git (fetch)
upstream        https://github.com/treehouses/treehouses.github.io.git (push)

fix link

link in picture below goes to "sorry, page you are looking for doesn't exist" error

Here is a picture of the error page:

I suggest to edit the link so it goes to the proper page

move download.md to right directory structure

Privacy Policy for play store

fix security issues

https://github.com/treehouses/treehouses.github.io/network/alerts

Add stop Docker container clarification for Nextcloud (Step 7)

In order to avoid containers from conflicting and causing issues with tor loading Nextcloud, if would be helpful to add a clarification clause to:

Now that the container has been created, you can stop and start it with docker stop nextcloud and docker start nextcloud. To view all running and stopped containers, run docker ps -a.

Something like:

Note: use docker stop <container> on any running containers other than Nextcloud.

Wording on Step 6 a little confusing.

This is a small issue, but on step 6, it says this- "Therefore, open a command line and open your username.github.io repository on the GitHub user interface. You then need to copy the link provided in the repository.
Then, turn to your command prompt and type your repository URL in the form of git clone https://github.com/EmilyLarkin/EmilyLarkin.github.io.git into the command line. Be sure to use the correct URL to clone your repository (you will obviously type your own username). "

So first we copy the url to clone it, but then it goes on to say "type git clone https://github.com/EmilyLarkin/EmilyLarkin.github.io.git" This is somewhat confusing because it sounds like we need to type just that with our name and the copy we made of the url isn't needed yet. My clone wasn't called this, so if I typed this with my name it wouldn't work. Maybe it should say something like, type git clone and then paste the url you copied. Just an idea to make it a little more clear!

Navigate to track VI's process

On step 9
Direction tells user to view the process via process tracking web.
https://treehouses.io/#!pages/vi/firststeps.md#Step_9_-_Be_Part_of_the_Team

NOTE: You can track your progress with the number of pull requests and issues here.

However, this fails to link users to trackprogress.md.

Issue and PR templates

https://help.github.com/en/articles/about-issue-and-pull-request-templates

Inaccurate description for power supply for Raspberry Pi

https://treehouses.io/#!./pages/vi/firststeps.md#Pre-Requisites
The description below says "Power cord", more accurate description should be "Power supply"

2. Power cord for the Pi
   • Standard USB-C power cord: 3.0A for Pi 4
   • Micro USB power cord: 2.5A for Pi 3B/3B+

If you agree I will be working this issue.

add flowchart

In step 6 "GitHub Issues" there is a missing flowchart diagram. I suggest adding a diagram in place of the "NEED DIAGRAM HERE" text (see picture below)

here is the flowchart I have drafted:

DebianforWindowsIssue

The First Steps for System VI's does needs a Debian for Windows instruction section

cmd

edit text in issues

Edit the reasons why an issue may be denied. currently the formatting is off where some words are italicized others are not and there is a random line break

Dead link on the web

I found the link problem in Git issue tutorial.

https://treehouses.io/#!./pages/vi/github-issues.md

NOTE: Remember to always sync your fork before starting to work on a new issue. To sync your fork you can follow the process in the previous step.

This block contains a dead link. I known that you refer to this link https://treehouses.io/#!./pages/vi/gitrepositories.md which has the Sync Your Fork section.

FAQ Page missing an alternative use for 'YourUserName.github.io'

Posting an explanation on how to create an organization and using that user name in lieu of 'yourusername' needs to be added to the FAQ page; or instead of referencing the FAQ page for the alternative, have it listed in step 3.

step1: add note to make sure latest image gets downloaded

Fix treehouses.github.io link

Currently treehouses.github.io repository link is pointing to https://github.com/treehouses.github.io it needs to be pointed to https://github.com/treehouses/treehouses.github.io

"NEED DIAGRAM HERE" in github-issues.md

Looks like the "Forking Workflow" diagram is missing in https://treehouses.io/#!./pages/vi/github-issues.md , with a placeholder "NEED DIAGRAM HERE".

Probably time to create the diagram and put it there.

Command missing from Step 7 (Nextcloud)

The command to start the tor service which allows users to access Nextcloud is missing.

Start up Tor
As we have run Nextcloud on port 8080, that's the port that we will have to open up with Tor. >While still in the root of treehouses, run treehouses tor add 80 8080, treehouses tor notice on, >then treehouses tor to find the tor address. You should see something like this:

Should be:

Start up Tor
As we have run Nextcloud on port 8080, that's the port that we will have to open up with Tor. >While still in the root of treehouses, run treehouses tor add 80 8080, treehouses tor notice on, >treehouses tor (to find the tor address), and then treehouses tor start. You should see something like this:

add a fork me on github somewhere

best would be top right corner ;)

SSH clarity for Step 7 (Nextcloud).

Step 2 walks through how to set up the SSH keys and then step 7 (Nextcloud) requires a fresh image with a rewrite to autorunonce. There's no mention on readding the prior made key back into the RPi, yet it requests that the user ssh into the RPi which can prompt an error.

I feel it would be beneficial to add:

"If you encounter an SSH error such as

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@> > @@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@> @@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:nVgL71cf8dHCqarTM8ld4wVvaAnE+vMEn+bFRbL+EPQ.
Please contact your system administrator.
Add correct host key in /home/hipr/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/hipr/.ssh/known_hosts:1
  remove with:
  ssh-keygen -f "/home/hipr/.ssh/known_hosts" -R 192.168.1.189
ECDSA host key for 192.168.1.189 has changed and you have requested strict checking.
Host key verification failed.

then proceed to run the command ssh-keygen -f "/home/username/.ssh/known_hosts" -R <local ip-address>, followed by sudo treehouses sshkey add "SSH key" to reinsert your ssh made in step 2."

Thoughts?

step0 on the end while waiting for rpi order to come

... add note that you can jump to step3 in the between time

remove background form red text

lowercase "d" for Dogi in trackprogress.md

Add content for "Introductory Step"

I have been using this WSL for a while and see that it has offer a real terminal experience as well as built in git and common editors. As a part of Setting up your environment for window device, this WSL is essential for command tools for developers. Couple command lines will quickly get this WSL running. @ArranHL @dogi @lmmrssa.

Is it possible that we can add an installation guide for this tool other than putty or git bash?
Raw Git Hack file I want to add.

Setting up your environment