TheFern2

from pyfirmata import Arduino, util
import time
from eip import PLC

def boolean_read(tag):
  '''
  simple tag read
  '''
  return comm.Read(tag)

TheFern2

Name: Flash 
Serial: eNrzzU/OLi0odswsqnHLSSzOqDGoca7JKCkpsNLXLy8v1ytJTczVLUotKNFLzs8FAJHYETc=

if anyone wants to thank ETH: 0x527c2aB55b744D6167dc981576318af96ed26676
Thank you!

TheFern2

" General Settings {{{
set nocompatible "vim, not vi
filetype plugin indent on
set number
set tabstop=4
set background=dark
syntax enable
set laststatus=2
" }}}

TheFern2

Setup

Once droplet is spinning, run through initial server setup:

Initial Server Setup Setup formatted as markdown for future reference

Introduction

When you first create a new Ubuntu 18.04 server, there are a few configuration steps that you should take early on as part of the basic setup. This will increase the security and usability of your server and will give you a solid foundation for subsequent actions.

Note: The guide below demonstrates how to manually complete the steps we recommend for new Ubuntu 18.04 servers. Following this procedure manually can be useful to learn some basic system admi

TheFern2

Aliases

In order to keep bashrc or bash_profile clean, aliases should go in the bash_aliases file. Add below IF to bashrc.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

TheFern2

Install Pip Packages

If you want to test a PIP package located in a local git repository you can do it this way:

pip install git+file:///path/to/your/git/repo

TheFern2

Better commit messages

This is my custom commit message:

# If this commit is applied, it will... (Less than 50 chars)

# Why was this change made?

# How does it address the issue?

TheFern2

Updating a feature branch

First we'll update your local master branch. Go to your local project and check out the branch you want to merge into (your local master branch)

$ git checkout master

Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to master will be stored in a local branch, remotes/origin/master

TheFern2

It's not immediately obvious how to pull down the code for a PR and test it locally. But it's pretty easy. (This assumes you have a remote for the main repo named upstream.)

Getting the PR code

1. Make note of the PR number. For example, Rod's latest is PR #37: Psiphon-Labs/psiphon-tunnel-core#37

2. Fetch the PR's pseudo-branch (or bookmark or rev pointer whatever the word is), and give it a local branch name. Here we'll name it pr37:

$ git fetch upstream pull/37/head:pr37

TheFern2

#! /bin/sh

# Start from the repository root.
cd ./$(git rev-parse --show-cdup)

# Delete .pyc files and empty directories.
# These files become a problem when switching branches
# if pycache is there with pyc even as an empty folder it will show up
# on another branch under vscode, this fixes that.
# @kodaman2