Open ssl.conf in a text editor.
Edit the domain(s) listed under the [alt_names] section so that they match the local domain name you want to use for your project, e.g.
DNS.1 = my-project.dev
Additional FQDNs can be added if required:
| // Reference : https://egghead.io/lessons/javascript-redux-implementing-combinereducers-from-scratch | |
| const combineReducers = (reducers) => { | |
| return ( state = {}, action) => { | |
| const keys = Object.keys(reducers); | |
| const arr = keys.reduce((accumulator, key) => { | |
| // since accumulator is created inside reducer function we don't have to worry about if it's mutable or not. | |
| // reducer still stays as a pure function. | |
| accumulator[key] = reducers[key](state[key],action); | |
| return accumulator; |
| RUN apt update | |
| RUN apt upgrade -y | |
| RUN apt install -y apt-utils | |
| RUN a2enmod rewrite | |
| RUN apt install -y libmcrypt-dev | |
| RUN docker-php-ext-install mcrypt | |
| RUN apt install -y libicu-dev | |
| RUN docker-php-ext-install -j$(nproc) intl | |
| RUN apt-get install -y libfreetype6-dev libjpeg62-turbo-dev libpng12-dev | |
| RUN docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ |
Follow the steps below if you are interested in creating your own custom configurable Couchbase docker image. You will start off with the official Couchbase Enterprise docker image that is available on Docker Hub and use the Couchbase CLI and REST interface to create a custom configurable image.
This approach inspired by the tutorial. We essentially built a custom docker image from the base Coucbase server image that is configured for our development needs!
DockerFile and open it using an editor of your choiceDockerFile.| import 'dart:async'; | |
| import 'package:flutter/material.dart'; | |
| class InfiniteScroll extends StatefulWidget { | |
| @override | |
| _InfiniteScrollState createState() => new _InfiniteScrollState(); | |
| } | |
| class _InfiniteScrollState extends State<InfiniteScroll> { |
| #!/bin/bash | |
| # https://www.nginx.com/resources/wiki/start/topics/tutorials/install/ | |
| # Switch to root | |
| sudo su | |
| # Add the mainline release | |
| echo "deb http://nginx.org/packages/mainline/ubuntu/ xenial nginx | |
| deb-src http://nginx.org/packages/mainline/ubuntu/ xenial nginx" > /etc/apt/sources.list.d/nginx.list |
| == Adb Server | |
| adb kill-server | |
| adb start-server | |
| == Adb Reboot | |
| adb reboot | |
| adb reboot recovery | |
| adb reboot-bootloader | |
| == Shell |
Transforming elements can be interesting if you're a library author, but can also be very valuable when writing components to abstract behaviour in your existing code base.
To get a better understanding, we will walkthrough the most important React Top Level API transformation functionalities. React offers a couple of helper functions that we can leverage when for creating and adapting elements, further information is available via the official React documentation.
| # | |
| # Building V8 for alpine is a real pain. We have to compile from source, because it has to be | |
| # linked against musl, and we also have to recompile some of the build tools as the official | |
| # build workflow tends to assume glibc by including vendored tools that link against it. | |
| # | |
| # The general strategy is this: | |
| # | |
| # 1. Build GN for alpine (this is a build dependency) | |
| # 2. Use depot_tools to fetch the V8 source and dependencies (needs glibc) | |
| # 3. Build V8 for alpine |