Twitz Coding Session in Go — Cobra + Viper CLI with Initial Twitter + Cassandra Installation
Part 2 of 3 — Coding Session in Go — Cobra + Viper CLI for Parsing Text Files, Retrieval of Twitter Data, Exports to various file formats, and export to Apache Cassandra.
UPDATED PARTS:
- Twitz Coding Session in Go — Cobra + Viper CLI for Parsing Text Files
- Twitz Coding Session in Go — Cobra + Viper CLI with Initial Twitter + Cassandra Installation (this post)
- Twitz Coding Session in Go — Cobra + Viper CLI Wrap Up + Twitter Data Retrieval
Updated links to each part will be posted at bottom of this post when I publish them. For code, written walk through, and the like scroll down below the video and timestamps.
Hacking Together a CLI Installing Cassandra, Setting Up the Twitter API, ENV Vars, etc.
0:04 Kick ass intro. Just the standard rocking tune.
3:40 A quick recap. Check out the previous write “Twitz Coding Session in Go — Cobra + Viper CLI for Parsing Text Files” of this series.
4:30 Beginning of completion of twitz parse command for exporting out to XML, JSON, and CSV (already did the text export previous session). This segment also includes a number of refactorings to clean up the functions, break out the control structures and make the code more readable.
In the end of refactoring twitz parse came out like this. The completed list is put together by calling the buildTwitterList() function which is actually in the helpers.go file. Then prints that list out as is, and checks to see if a file export should be done. If there is a configuration setting set for file export then that process starts with a call to exportParsedTwitterList(exportFilename string, exportFormat string, ... etc ... ). Then a simple single level control if then else structure to determine which format to export the data to, and a call to the respective export function to do the actual export of data and writing of the file to the underlying system. There’s some more refactoring that could be done, but for now, this is cleaned up pretty nicely considering the splattering of code I started with at first.
50:00 I walk through a quick install of an Apache Cassandra single node that I’ll use for development use later. I also show quickly how to start and stop post-installation.
Reference: Apache Cassandra, Download Page, and Installation Instructions.
53:50 Choosing the go-twitter API library for Go. I look at a few real quickly just to insure that is the library I want to use.
Reference: go-twitter library
56:35 At this point I go through how I set a Twitter App within the API interface. This is a key part of the series where I take a look at the consumer keys and access token and access token secrets and where they’re at in the Twitter interface and how one needs to reset them if they just showed the keys on a stream (like I just did, shockers!)
57:55 Here I discuss and show where to setup the environment variables inside of Goland IDE to building and execution of the CLI. Once these are setup they’ll be the main mechanism I use in the IDE to test the CLI as I go through building out further features.
1:00:18 Updating the twitz config command to show the keys that we just added as environment variables. I set these up also with some string parsing and cutting off the end of the secrets so that the whole variable value isn’t shown but just enough to confirm that it is indeed a set configuration or environment variable.
1:16:53 At this point I work through some additional refactoring of functions to clean up some of the code mess that exists. Using Goland’s extract method feature and other tooling I work through several refactoring efforts that clean up the code.
1:23:17 Copying a build configuration in Goland. A handy little thing to know you can do when you have a bunch of build configuration options.
1:37:32 At this part of the video I look at the app-auth example in the code library, but I gotta add the caveat, I run into problems using the exact example. But I work through it and get to the first error messages that anybody would get to pending they’re using the same examples. I get them fixed however in the next session, this segment of the video however provides a basis for my pending PR’s and related work I’ll submit to the repo.
The remainder of the video is trying to figure out what is or isn’t exactly happening with the error.
I’ll include the working findem code in the next post on this series. Until then, watch the wrap up and enjoy!
1:59:20 Wrap up of video and upcoming stream schedule on Twitch.
UPDATED SERIES PARTS
