gabrieljoelc

Applied distributed system communication stuff

Scenario

Frontend API (FA):

1. User adds wallet
2. User KYC verifies
3. User changes wallet
4. User changes wallet

efekarakus

Parameters:
  App:
    Type: String
    Description: Your application's name.
  Env:
    Type: String
    Description: The environment name your service, job, or workflow is being deployed to.
  Name:
    Type: String
    Description: The name of the service, job, or workflow being deployed.

ynwd

Clear Cache

docker-compose rm -fv db

spettifer

# The application_type attribute is now case senstive. If the resource has been previously created with provider v1.x and the 
# application_type was not lower case, then changing it to suit the v2 provider will result in the resource being destroyed 
# and re-created since there is no way to update this value in place 
# (see https://github.com/terraform-providers/terraform-provider-azurerm/issues/5902). 
  
# To prevent this, add a lifecycle customisation and specify application_type as an attribute to ignore. Any attribute specified
# in the ignore_changes array will not be considered when creating a plan for an update, but they will still be part of creating
# a new resource.
  
resource "azurerm_application_insights" "appinsights" {

spk

# https://github.com/marketplace/actions/checkout
# https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#issue-comment-event-issue_comment
# https://devcenter.heroku.com/changelog-items/775
# https://github.com/actions/checkout#fetch-all-history-for-all-tags-and-branches
# https://github.com/cirrus-actions/rebase#installation
# https://github.com/actions/heroku/issues/10
---
name: Deploy to HEROKU_APP_NAME

on:

gabrieljoelc

%author: Gabriel Chaney %date: 2019-06-25

-> Mind of a Chef Software Engineer <-

-> What a non-engineer should know about how an engineer thinks. <-

---

brentvatne

We started building expo-firebase based off of react-native-firebase in order to attempt to get it to work well within the Expo client. It turned out that there wasn't a good way to do this - the SDK fully expects that there is one binary per app, and the Expo client has multiple apps inside of it. We weren't able to work around this.

If you'd like to use Firebase in the Expo client with the managed workflow, we'd recommend using the Firebase JS SDK. It supports Firebase Realtime Database and Firebase Storage. If you'd like access to the full suite of native firebase tools, we recommend using the bare workflow and react-native-firebase, because we cannot support this in the Expo client currently.

• Firebase JS SDK: https://github.com/firebase/firebase-js-sdk
• React Native Firebase: https://github.com/invertase/react-native-firebase

gabrieljoelc

GistID: 87ded2e5fe0cfac465e57235c74c362e

Presented to Medumo engineering team 2019 Q1

Presentation specs:

• macOS Terminal with font size increased by 8
• vim with this config
• Goyo.vim
• Limelight.vim

alfianlosari

import React, { Component } from "react";

class Repos extends Component {
  componentDidMount() {
    window.addEventListener("scroll", this.handleOnScroll);
  }

  componentWillUnmount() {
    window.removeEventListener("scroll", this.handleOnScroll);
  }

alfianlosari

import gql from "graphql-tag";

export const trendingRepositoriesGQLQuery = gql`
  query search($query: String!, $cursor: String) {
    search(first: 15, query: $query, type: REPOSITORY, after: $cursor) {
      pageInfo {
        startCursor
        endCursor
        hasNextPage
        hasPreviousPage