I was trying to copy files to my Raspbian-based Raspberry Pi but I kept getting this error: ssh: connect to host 192.168.178.79 port 22: Connection refused Tell-tale Sign after few attempts the ssh status showed up an interesting set of logs: $> sudo service ssh status ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled) Active: active (running) since Mon 2017-04-10 08:51:38 UTC; 6min ago Main PID: 1332 (sshd) CGroup: /system.
Bitbucket is my main git repo for all my personal (PoC) projects, portfolio and all of my contracting projects - hands down on private repo. While I’ve tried Codeship, CircleCI, Jenkins for production use, however, all of these CI server needs some little education about private and public certificates for setting up roles/permission/access before any of them can pull out your source code and push it to eg: Amazon S3 — Pipelines + AWS S3 was far bit easier.
Copy & Paste, trust me! $> sudo apt-get update $> sudo apt-get upgrade $> sudo apt-get -y install git $> curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash $> source ~/.bashrc $> nvm install --lts as of this writing my NodeJS LTS version: v6.10.0 What’s The Fuss? Node Version Manager (nvm) gets installed, we’ll then use it to install whatever is the current NodeJS LTS - primarily behind the scenes, it will spear you from crap of load of these commands:
Short-lived scripts that sucked your resources for 1mins or at most 5mins - is probably fine. However, if it is recurring jobs in Cron and involves several tasks and at least an hour of processing - that’d be a different story. I was working on a simple NodeJS-based cron script with only 3 requirements: extract transform load Each one of these however would involve crunching through a million rows of data.
Wait, what ? Moving to Windows10 (6 months ago as of this writing) as my main OS is a bit hard, just a little bit. I use commandline ALL THE TIME and I can’t live without the developer’s Swiss army knife on my side - tiny tools that make our life easier: grep, sed, ps, tree, ssh, find … “Bash On Windows” was a good strategy from Microsoft - I didn’t bother about switching to Windows and I didn’t think twice, I was more worried about which machine to buy.
Yesterday 10th of Feb 2017, I managed to update my PC with the latest Windows 10 Insider Preview Build 15031. The list contains a massive set of features as well as fixes, so I didn’t mind the upgrade. It took at least 20mins to get it done. Once done, my NodeJS environment started complaining, btw I am using Node Version Manager. Here’s what I got when switching NodeJS versions:
I was working on transcoding videos into different formats, resolutions so it could be played on various desktops, tablets and mobile devices. My main working machine is Dell XPS13 on Windows 10 with Ubuntu Bash enabled, some of my needed libraries is missing and needs recompilation of FFmpeg the one that came from Ubuntu 14.04 repo. I think I’ve literraly spent hours or probably days buildin/re-building libraries just to get the videos transcoded into my desired format.
Since moving to Hugo few months ago my installation history with Go was quick and dirty, I just want to get something up running to get started with Hugo. 48 hours ago I was playing with Go, I thought of building a simple cli utility where CI server can hook in and start building something - of course it has be built on top of Go, enough to get my around its dev-ecosystem.
I was initially planning to use plain Github Pages for my blogging but I’ve read some good reviews with Hugo. I’ll give it a try and see how it goes. I have written a few blog posts over at Medium but I don’t want to spam my Twitter followers with random information that don’t matter to them. I might sync a few bits from time to time.