I hereby claim:
- I am riggtravis on github.
- I am trigg (https://keybase.io/trigg) on keybase.
- I have a public key ASArKMBcaGwanChHtkkgqpVkUv3jvgCwqpBhZepIgu1TZwo
To claim this, I am signing this object:
use git2; | |
fn main() { | |
let repo = git2::Repository::open(".").unwrap(); | |
let remotes: Vec<git2::Remote> = repo | |
.remotes() | |
.unwrap() | |
.iter() | |
.map(|remote| repo.find_remote(remote.unwrap()).unwrap()) | |
.collect(); |
I0219 15:05:22.561099 48632 factory.go:68] state store s3://{{CONFIG_BUCKET_REDACTED}} | |
I0219 15:05:22.731083 48632 s3context.go:194] found bucket in region "us-east-1" | |
I0219 15:05:22.731185 48632 s3fs.go:220] Reading file "s3://{{CONFIG_BUCKET_REDACTED}}/vault-cluster.k8s.local/config" | |
I0219 15:05:22.770509 48632 channel.go:97] resolving "stable" against default channel location "https://raw.githubusercontent.com/kubernetes/kops/master/channels/" | |
I0219 15:05:22.770542 48632 channel.go:102] Loading channel from "https://raw.githubusercontent.com/kubernetes/kops/master/channels/stable" | |
I0219 15:05:22.770560 48632 context.go:159] Performing HTTP request: GET https://raw.githubusercontent.com/kubernetes/kops/master/channels/stable | |
I0219 15:05:22.820062 48632 channel.go:111] Channel contents: spec: | |
images: | |
# We put the "legacy" version first, for kops versions that don't support versions ( < 1.5.0 ) | |
- name: kope.io/k8s-1.4-debian-jessie-amd64-hvm-ebs-2017-07-28 |
I hereby claim:
To claim this, I am signing this object:
In creating your senior project you should probably try to reduce all of your mental overhead as much as possible. And when I say probably I mean definitely. These are tools that will probably or definitely making your life easier. You shouldn't feel obliged to use any of these tools, but you should feel inspired by them to use some sort of tool to create your project.
Use web technologies to create desktop applications
SFIM stands for Standard Forum Interaction Modeling. The purose of the SFIM project is to create an ecosystem in which forums have a high level of interoperability. The idea is that any forum created using SFIM will have a well documented set of interactions that will be consistent. This way a forum administrator can port their interface manager from one forum manager software to another without having to also move data from one database to another. This way an android app developer can create a generic app that can be used to log into any SFIM forum, and a user can select any app targeting SFIM forums to access one or more of their favorite forums.