Posts

Showing posts from April, 2016

git: merge request

git checkout mastergit pullgit branch -b <mybranch><changes>git commit -am'My change commit'git push origin <mybranch>

Ubuntu LXD container: no IP address

sudo dpkg-reconfigure -p medium lxd Be very careful, this will wipe any existing lxc/lxd bridge you have and make your existing containers unreachable. So this is really only recommended if you are using LXD for the first time on your machine.

See comment section of https://www.stgraber.org/2016/03/11/lxd-2-0-introduction-to-lxd-112/

"This change was required to be able to decouple LXD from the old LXC tools, moving it onto its own bridge. The warning message was highlighting the reasons for that, the effect it would have on existing containers and how to configure it so things would work as usual."

openvpn confs - starpoint

server

port 1194 proto udp dev tun0 ca ca.crt cert server.crt key server.key # This file should be kept secret dh dh1024.pem server 192.168.100.0 255.255.255.0 ifconfig-pool-persist ipp.txt push "route 10.0.0.0 255.0.0.0" push "route 172.10.0.0 255.255.0.0" push "route 172.11.0.0 255.255.0.0" push "route 172.21.0.0 255.255.0.0" push "route 172.25.0.0 255.255.0.0" push "route 172.27.0.0 255.255.0.0" push "route 172.28.0.0 255.255.0.0" push "route 172.30.0.0 255.255.0.0" push "route 172.31.0.0 255.255.0.0" push "route 172.32.0.0 255.255.0.0" push "route 172.40.0.0 255.255.0.0" push "route 172.41.0.0 255.255.0.0" push "route 172.42.0.0 255.255.0.0" push "route 172.29.30.0 255.255.255.0" push "route 172.29.27.0 255.255.255.0" client-to-client keepalive 10 120 tls-auth ta.key 0 # This file is secret comp-lzo max-clients 200 user nobody group…

gist of git rebase problem avoidance

"If you treat rebasing as a way to clean up and work with commits before you push them, and if you only rebase commits that have never been available publicly, then you’ll be fine. If you rebase commits that have already been pushed publicly, and people may have based work on those commits, then you may be in for some frustrating trouble, and the scorn of your teammates."

https://git-scm.com/book/en/v2/Git-Branching-Rebasing

absolute necessities for technical teams of diverse personality types

change management for "real" using professional standards developed by large companies many government orgs use the standard existing tools may exist concepts definitely exist and are well documented repositories on all changed files who changed what when ability to lower repeated mistakes through good practices system for tracking pushes up environment chain dev -> qa -> staging -> prod garbage maintenance zero duplicate file name and/or paths requires code calling by old name/path be updated immediately process