masone

module.exports =
  api:
    host: process.env.api__host

  imagesApi:
    host: process.env.api__host

  designsApi:
    host: 'https://api.livingdocs.io'

masone

Webpack

webpack is a module bundler for the web

• https://webpack.js.org/
• https://webpack.js.org/concepts/modules/#what-is-a-webpack-module

Demo

http://localhost:3333

• Webpack dev server
• Fast live reload, incremental build
• JS/css example https://github.com/masone/legalwalls-web/blob/master/app/index.js

masone

change	time	impact
1%	Freitag 6.4. - 12:00
3%	Freitag 6.4. - 15:30
5%	Dienstag 10.4. - 8:30
Flipper cookie on all controllers	Dienstag 10.4. Nachmittag	we now get ~7% of the pageviews (employees and public) on local-ui. The response times in analytics start to increase. servers seem idle, so I interpret the problem is throughput, not server resources
3%	Dienstag Nachmittag	response times look better again
New Logstash	Mittwoch 11.4. - 8:50
Rails 5 Mittwoch	11.4. - 9:30 ~
Flipper switch redirect lui	11:20	if you see redirect loops, this is the one to revert

masone

LocalConfig status

Optional: Rename API methods

In the knowledge sharing session on LocalConfig, there was a bit of confusion about some of the API methods of the gem. The audience expected LocalConfig::Store#load_namespace! to load configs from kubernetes, which it doesn't actually do. It merely loads a hash into memory. LocalConfig.load_namespaces! on the other hand actually does load configmaps. But it additionally initializes the namespaces (including app, which is not a kubernetes configmap). Also, the boundaries between namespaces that build on shared kubernetes configmaps, namespaces that are just local objects are hard to grasp. Furthermore, we might want to distinguish clearly between custom namespaces the app explicitly registers and namespaces that are pre-populated by the gem.

I came up with a proposal in https://github.com/local-ch/local_config/pull/19, which has yet to be confirmed if it's less confusing or not. Maybe it's easier to decide once people start working with it. The g

masone

@Get(":id")
detail(@Param() param) {
  param // => undefined
}

masone

	Jul 08 13:20:09.965	__SENTRY__: { hub: [Hub] },
	Jul 08 13:20:09.965	members: [ [IncomingMessage], [ServerResponse] ],
	Jul 08 13:20:09.965	_maxListeners: undefined,
	Jul 08 13:20:09.965	_eventsCount: 3,
	Jul 08 13:20:09.965	error: [Function] },
	Jul 08 13:20:09.965	newListener: [Function: updateExceptionCapture],
	Jul 08 13:20:09.965	removeListener: [Function: updateExceptionCapture],
	Jul 08 13:20:09.965	[Object: null prototype] {
	Jul 08 13:20:09.965	_events:
	Jul 08 13:20:09.965	domain: null,

masone

import { parseCookies, setCookie as setNookie } from "nookies"

const onetrustFirstPartyHandler = (req, res, next) => {
  const cookies = parseCookies({ req })

  const setCookie = (name) => {
    const value = cookies[name]
    if (value) {
      setNookie({ res }, name, value, {
        httpOnly: false,