supertopher

day 23

I no longer hear the beeping in the yard next door. -- Topher

day 27

Projects at work are disapearing. Called Jenine back. Bernie dropped out yesterday. Outlook is grim, but it's good to be in Colorado with Teresa

Day 30 Easter

teresa made cinnamon rolls. It snowed today and the stream that i diverted has higher flow today because of the snow. It's cleared out the pond scum in both of the less used streams. Me and Teresa are both Tired. We started watching Ozark. Teresa is sick with possibly Corona. I slept in Summer for more qurantine.

supertopher

Steps

1. Wait for clock devices to read something like maybe 5
2. Head to the city
3. Meet up near Yerba Buena or out by Josh depending on activity choice
4. Walk around alot
5. Change this plan if sock's foot is defective
6. Eat food

supertopher

Building Opsmanager on a stemcell using packer

Understanding the landscape:

The opsman appliance will be built to some degree using the built in tooling on the machine running the packer script. This means that either your computer or the Dockerfile will have an effect on your build. Beware version changes from your workstation to the ci build. Specifically we version lock Go, virtualbox, packer, node, phantomjs, and terraform within the docker image.

Once you have an environment capable of running the packer scripts you can run be rake "vm:create[$IAAS]" Each IAAS works a bit differently. Some appliances are built using local VMs where others are built using the API of the IAAS to spin up virtual machines native to that IAAS. In the case of both google and aws you will need to provide a means to authentica

supertopher

Upgrading to Concourse verison 1.4.0

• At this moment the SF cloud ops team believes that upgrading to the latest version of concourse has some external networking issues.

• We are unsure if these issues are due to runC, 1.4.0, or some yet undiscovered problem.

• The upgrade also failed for us while upgrading the database, and reverting back to 1.2.0 was unsuccessful. We think at this moment we are stuck on 1.4.0 unless we tear down the whole deployment

• With that said we suggest staying away from the latest verion of concourse until we can dig into the problem a bit more over here.

supertopher

#!/bin/sh
# set -e

cd part-2
bundle
bundle exec rake db:drop
bundle exec rake db:create
bundle exec rake db:migrate
bundle exec rake db:test:prepare

supertopher

# 1. Require the gem sqlite3.  You must `gem install sqlite3` if you get an error
# stating `cannot load such file -- sqlite3`
# This will add the gem to your local gemset
require 'firebase'
require 'faker'

# 2. Sign up for a firebase account and set the uri here
base_uri="https://luminous-fire-2162.firebaseio.com/"

# 3. Set up a connection to the database you have created

supertopher

Topher's Recommended Laptops

Macbook Air 11"

Specs:

• 1.7 Ghz Dual Core i7
• 8GB RAM
• 128 GB hard drive
• Upgradable to 256GB

supertopher

Congratulations on making the cut for Dev Bootcamp!

This tutorial is going to help you start off on the right foot by teaching you a few things that aren't Ruby. These things are, however, important to undestand for your future in the industry. If you are running MacOS or any flavor of Linux you are going to be very comfortable fitting into a Ruby workflow. Windows users will find that since so much of Ruby workflow is based on shell tools (and Windows has no real linux shell support) life is going to be a bit more interesting.

Furthermore all staff (and and an overwhelming majority of Rubyists) use OSX. If you are on windows either get dirty and start solving these problems for yourself or check out Rails Installer

OSX Users you could of course also use Rails Installer, however, as is true or so many things pre-packaged for you: this quick boost will be a net drag in the long-term. We would prefer that you build your environment yourself s

supertopher

Automated Testing.

Testing is helpful for ensuring that your code runs (driver code). This is to make sure that current features work, old features still work, and future work will be easily tested. By default, every Rails application has three environments: development, test, and production.

Rails offers three kinds of testing:

• Unit tests: 
In the context of Rails, unit tests are meant primarily to cover the domain logic in your models, which include things like validations, calculations, search methods, and any other interesting functionality that your models implement.
• Functional tests: These provide a way to verify that the actions for a single controller are working as expected, and allow you to do things such as post data to a specific action and verify the correct response is returned
• Integration tests: Any given session with a Rails application will span across several models and controllers. Integration tests provide a way to test those kinds of interactions. Essentia

supertopher

<!doctype html>
<html>

  <head>
    <link rel="stylesheet" href="http://cdn.jsdelivr.net/normalize/2.1.0/normalize.css">
    <link rel="stylesheet" href="main.css">
    <link rel="stylesheet" href="http://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700,800">
    <link rel="stylesheet" href="http://fonts.googleapis.com/css?family=Lato:100,900">
    <link rel="stylesheet" href="http://cdnjs.cloudflare.com/ajax/libs/font-awesome/3.0.2/css/font-awesome.min.css">
  </head>