profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/tyler-eon/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Tyler Eon tyler-eon California http://eon.dev Solution Architect

toothrot/amplitude-api 45

A Ruby library for interacting with the Amplitude API

tyler-eon/bertjs 4

A JavaScript library for encoding and decoding BERT data. Primarily targeted for use with WebSocket.

tyler-eon/acls 3

ACLS is a library for autoloading Ruby source files in one or more directory trees.

tyler-eon/blaze 2

A friendlier interface to Google Cloud Firestore.

tyler-eon/erldeps 1

Simple dependency module for starting and stopping Erlang applications.

tyler-eon/activerecord-postgis-adapter 0

ActiveRecord connection adapter for PostGIS, based on postgresql and rgeo

tyler-eon/amplitude-api 0

A Ruby library for interacting with the Amplitude API

tyler-eon/antigen 0

A plugin manager for zsh, inspired by oh-my-zsh and vundle.

tyler-eon/arc 0

:paperclip: Flexible file upload and attachment library for Elixir

tyler-eon/arc_gcs 0

Provides an Arc backend for Google Cloud Storage

pull request commenttyler-eon/waffle_gcs

Fix config storage module name in README.md

That's really up to the new maintainers to decide. They can cherry-pick the edits if they'd like or rewrite it in their own style, either way is good.

michallepicki

comment created time in 7 days

pull request commenttyler-eon/waffle_gcs

Fix config storage module name in README.md

@michallepicki Yes, the repo you linked to has officially taken over for this one. I'm not sure if they've pushed a new update to hex.pm yet but unfortunately I don't have the time even just to help manage this project let alone helm it, so I've passed the baton to @almirsarajcic .

If hex.pm doesn't have a package published pointing to the new updates I would recommend having hex pull from github to grab the latest version from the @almirsarajcic fork.

michallepicki

comment created time in 7 days

delete branch tyler-eon/waffle_gcs

delete branch : gapi_0.14

delete time in a month

push eventtyler-eon/waffle_gcs

Tyler Eon

commit sha fc5cabaef483f8fa8bb77299707ee119c1c86d8a

Update to Google Storage APIs v0.14 After commenting my findings on [this](https://github.com/googleapis/elixir-google-api/issues/972) issue, it turns out that there's no good way to automate uploading binary data and it needs to be hard-coded, similar to how the other Google Storage API clients do it. This new function is called `storage_objects_insert_iodata` and allows a binary (string) or iolist to be used when performing a multipart upload.

view details

Tyler Eon

commit sha c24967cc4b80e086adcf24d818e6b6416559eb54

Merge pull request #1 from tyler-eon/gapi_0.14 Update Google Storage APIs

view details

push time in a month

PR merged tyler-eon/waffle_gcs

Update Google Storage APIs

After commenting my findings on this issue, it turns out that there's no good way to automate uploading binary data and it needs to be hard-coded, similar to how the other Google Storage API clients do it. This new function is called storage_objects_insert_iodata and allows a binary (string) or iolist to be used when performing a multipart upload.

+29 -81

3 comments

4 changed files

tyler-eon

pr closed time in a month

push eventtyler-eon/waffle_gcs

Almir Sarajčić

commit sha 31c61623560312bb20a3490d3f70463c9536034d

Update waffle

view details

Almir Sarajčić

commit sha f62f0cdab4d25140e43694a9bee1288efcc1576e

Fix CDN issue

view details

Almir Sarajčić

commit sha 28e5fd61623bb61dc71692031de91d88050b91cc

Add test for CDN fix

view details

Almir Sarajčić

commit sha e23f3f3bd78922665a409ea7e851eaf9e51fd946

Support setting object metadata

view details

Almir Sarajčić

commit sha 9a94ab51882085d6d25e398debcc30f6da5fe838

Add documentation

view details

Ian Young

commit sha fa5fb988118e4c8af07409bd88f1779ee6c4f64b

Add storage to config example in readme

view details

Monte

commit sha 15950128b7dc32467d8e05cc9414404eff956145

Fix for deleting objects: object path must be URL percent-encoded. Requests to delete individual versions were failing but the errors do not bubble up.

view details

Almir Sarajčić

commit sha c20c5a5735ff07a45f3ee982a49f998694805bdc

Merge pull request #1 from montebrown/various-fixes Fix for deleting objects: object path must be URL percent-encoded.

view details

Tyler Eon

commit sha c3cb7adfa3d41fc369347b3e0686e5437c031d0e

Merge pull request #6 from almirsarajcic/various-fixes Various fixes

view details

Tyler Eon

commit sha d1526e0b2a88da63eeb24d05d8f6e6bf28bb3ea6

Merge pull request #7 from GimletMedia/readme_config Add storage to config example in readme

view details

Tyler Eon

commit sha fc5cabaef483f8fa8bb77299707ee119c1c86d8a

Update to Google Storage APIs v0.14 After commenting my findings on [this](https://github.com/googleapis/elixir-google-api/issues/972) issue, it turns out that there's no good way to automate uploading binary data and it needs to be hard-coded, similar to how the other Google Storage API clients do it. This new function is called `storage_objects_insert_iodata` and allows a binary (string) or iolist to be used when performing a multipart upload.

view details

push time in a month

pull request commenttyler-eon/waffle_gcs

Update Google Storage APIs

@achempion I was originally waiting to try and resolve the CI issues before merging this but I'll just resolve the merge conflicts and force the merge for now since this particular repo isn't really active at the moment but I still want to remove my hack sooner rather than later for anyone that wants to use this code.

tyler-eon

comment created time in a month

delete branch rearc/quest

delete branch : readme-update

delete time in a month

push eventrearc/quest

Tyler Eon

commit sha 097957e3f88f8f3dc2bd259cbe31ba6410a5403e

Update readme for clarity and added git info We want the instructions to be as clear as possible so that candidates don't unnecessarily get hung up on certain details and focus on the right aspects of the challenge. Additionally, we want candidates to show their git skills if they have any, so we're adding instructions to create a git repo for the submission if the candidate knows and can use git to do so.

view details

Tyler Eon

commit sha 3be26b52f285a80b25558ae019fca6604b19e171

Merge pull request #26 from rearc/readme-update Update readme for clarity and added git info

view details

push time in a month

PR merged rearc/quest

Update readme for clarity and added git info

We want the instructions to be as clear as possible so that candidates don't unnecessarily get hung up on certain details and focus on the right aspects of the challenge.

Additionally, we want candidates to show their git skills if they have any, so we're adding instructions to create a git repo for the submission if the candidate knows and can use git to do so.

+74 -46

3 comments

1 changed file

tyler-eon

pr closed time in a month

push eventrearc/quest

Tyler Eon

commit sha 097957e3f88f8f3dc2bd259cbe31ba6410a5403e

Update readme for clarity and added git info We want the instructions to be as clear as possible so that candidates don't unnecessarily get hung up on certain details and focus on the right aspects of the challenge. Additionally, we want candidates to show their git skills if they have any, so we're adding instructions to create a git repo for the submission if the candidate knows and can use git to do so.

view details

push time in a month

pull request commentrearc/quest

Update readme for clarity and added git info

Since we added CDK as an option, there are a few more places where we should mention it (where tf and cf are already mentioned) for completeness. Or just shorten them all to "IaC" in all but one place.

Done. I like the idea of using just "IaC" and I've also expanded the definition to include whichever IaC of choice the candidate is comfortable with. @rahulsen would you agree that if someone can learn and use, e.g., CloudFormation successfully then they could learn and use Terraform successfully? That's the assumption I am thinking we can make by letting them choose whatever IaC path they want. However, I am specifically calling out Terraform as being preferred since most companies want to move in that direction and it's becoming a cloud-agnostic choice for many. Thoughts?

tyler-eon

comment created time in a month

push eventrearc/quest

Tyler Eon

commit sha 6eeb130ec4df4cbd2811daca7c629ebaea3400ea

Update readme for clarity and added git info We want the instructions to be as clear as possible so that candidates don't unnecessarily get hung up on certain details and focus on the right aspects of the challenge. Additionally, we want candidates to show their git skills if they have any, so we're adding instructions to create a git repo for the submission if the candidate knows and can use git to do so.

view details

push time in a month

PullRequestReviewEvent

Pull request review commentrearc/quest

Update readme for clarity and added git info

 # A quest in the clouds -### Q. What is this quest ?-#####  It is a fun way to assess your cloud skills. It is also a good representative sample of the work we do at Rearc. Quest is a webapp made with node.js and golang.--### Q. Do i need to be an expert in node.js and golang ?-#####  No. The starting point of the quest app is `npm install && npm start`. That is all the node.js you need to know. And you wont even see golang.--### Q. So what skills should i have ?-#####  AWS. Cloud concepts. Docker (containerization). IAC (Infrastructure as code). HTTP/HTTPS. Linux/Unix.--### Q. What do i have to do ?-#####   1) Deploy the app in AWS and find the secret page. Use Linux 64-bit as your OS (Amazon Linux preferred)-#####   2) Deploy the app in a Docker container. Use `node:10` as the base image-#####   3) Inject an environment variable (SECRET_WORD) in the docker container. The value of SECRET_WORD should be the secret word discovered on the secret page-#####   4) Deploy a loadbalancer in front of the app-#####   5) Complete "Terraform"ing and/or "Cloudformation"ing the entire stack for "single click" deployment (Use the latest version of Terraform available at the time)-#####   6) Add TLS (https). Its OK to use locally generated certs.--### Q. How do i know i have solved these stages ?-#####  Each stage can be tested as follows (where <ip_or_host> is the location where the app is deployed) -#####   1) AWS/Secret page - `http(s)://<ip_or_host>[:port]/`-#####   2) Docker - `http(s)://<ip_or_host>[:port]/docker`-#####   3) SECRET_WORD env variable - `http(s)://<ip_or_host>[:port]/secret_word`-#####   4) Loadbalancer - `http(s)://<ip_or_host>[:port]/loadbalanced`-#####   5) Terraform and/or Cloudformation - we will test your submitted templates in our AWS account-#####   6) TLS - `http(s)://<ip_or_host>[:port]/tls`--### Q. Do i have to do all these ?-#####  You can do as many as you like. We suspect though that once you start you wont be able to stop. Its addictive.--### Q. What do i have to submit ?-#####   1) Terraform and/or Cloudformation template(s) (if you complete stage 5)-#####   2) Dockerfile (if you complete stages 2 and 3)-#####   3) Screenshot of the secret page (if you complete stage 1)-#####   4) URL of your stack (if the endpoint is exposed)--### Q. What if i successfully complete all the challenges ?-#####  We have many more for you to solve as a member of the Rearc team !--### Q. What if i find a bug ?-#####  Awesome! Lets talk.--### Q. What if i fail ?-#####  Do. Or do not. There is no fail.--### Q. Can i share this quest with others ?-##### No.+### Q. What is this quest?++It is a fun way to assess your cloud skills. It is also a good representative sample of the work we do at Rearc. Quest is a webapp made with node.js and golang.++### Q. Do I need to be an expert in node.js and golang?++No. The starting point of the quest app is `npm install && npm start`. That is all the node.js you need to know. And you wont even see golang.++### Q. So what skills should I have?++AWS. General concepts, especially networking. Docker (containerization). IaC (Infrastructure as code). Linux/Unix. Git. TLS certs is a plus.++### Q. What do I have to do?++1. If you know how to use git, start a git repository (local-only is acceptable) and commit all of your work to it.+2. Deploy the app in AWS and navigate to the index page. Use Linux 64-bit as your OS (Amazon Linux preferred).+3. Deploy the app in a Docker container. Use `node:10` as the base image.+4. Inject an environment variable (`SECRET_WORD`) in the Docker container. The value of `SECRET_WORD` should be the secret word discovered on the index page of the application.+5. Deploy a load balancer in front of the app.+6. Complete Terraform-ing and/or CloudFormation-ing the entire stack for "single click" deployment (Please use Terraform v1+).+7. Add TLS (https). You may use locally-generated certs.++### Q. How do I know I have solved these stages?++Each stage can be tested as follows (where <ip_or_host> is the location where the app is deployed) ++1. Index page (contains the secret word) - `http(s)://<ip_or_host>[:port]/`+2. Docker check - `http(s)://<ip_or_host>[:port]/docker`+3. Secret Word check - `http(s)://<ip_or_host>[:port]/secret_word`+4. Load Balancer check  - `http(s)://<ip_or_host>[:port]/loadbalanced`+5. TLS check - `http(s)://<ip_or_host>[:port]/tls`+6. Terraform and/or CloudFormation - Manually checked when your quest is submitted.++### Q. Do I have to do all these?++You may do whichever, and however many, of the tasks above as you'd like. We suspect that once you start, you won't be able to stop. It's addictive.++### Q. What do I have to submit?++1. Your work assets, as one or both of the following:+  - A link to a hosted git repository.+  - A ZIP file containing your project directory. Include the `.git` sub-directory if you used git.+2. Proof of completion, as one or both of the following:+  - A link to a hosted AWS deployment.+  - One or more screenshots showing, at least, the index page of the final deployment.++Your work assets should include:++- Terraform or CloudFormation modules, if you completed that task.

Added CDK.

Side note: we might want to eventually think about letting people host this on at least Google Cloud as well, if they choose to do so, as it's still relatively similar to AWS. I wouldn't mind allowing Azure deployments either but it does differ significantly from AWS and GCP.

tyler-eon

comment created time in a month

push eventrearc/quest

Tyler Eon

commit sha 9999c6672009344ce3d338b80046b47fac905efc

Update readme for clarity and added git info We want the instructions to be as clear as possible so that candidates don't unnecessarily get hung up on certain details and focus on the right aspects of the challenge. Additionally, we want candidates to show their git skills if they have any, so we're adding instructions to create a git repo for the submission if the candidate knows and can use git to do so.

view details

push time in a month

PR opened rearc/quest

Update readme for clarity and added git info

We want the instructions to be as clear as possible so that candidates don't unnecessarily get hung up on certain details and focus on the right aspects of the challenge.

Additionally, we want candidates to show their git skills if they have any, so we're adding instructions to create a git repo for the submission if the candidate knows and can use git to do so.

+73 -46

0 comment

1 changed file

pr created time in a month

create barnchrearc/quest

branch : readme-update

created branch time in a month

issue commentkolorahl/waffle_gcs

Is this project dead?

@harrygr I can try to investigate why the Travis build failed and see if the solution is simple, hopefully just ensuring the appropriate bucket exists is enough, but ultimately I do not have enough free time at the moment to ensure that this repository is maintained and kept up-to-date. It looks like that could change in the near future, so fingers crossed for that.

I can confirm that version 0.1.1 (if that's still on hex.pm) was my last officially-published package from this repo. I'm pretty sure it worked (at least 99% working, certainly in all the common use cases). If you want to stick with that version for now, feel free. I transferred ownership of the repo to @almirsarajcic so any future versions would come from his repo. I may end up either fixing this one (my repo) or look to assisting with the new repo if I get the time to do so.

TL;DR

The fork (by @almirsarajcic) is the new official version of this package. Version 0.1.1 is the last published version of the package from my repo, and should be in a working condition for all common use cases. You might be able to use it, at least temporarily, if you are experiencing issues with newer versions.

lstrzebinczyk

comment created time in 3 months