See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
The only way I've succeeded so far is to employ SSH.
Assuming you are new to this like me, first I'd like to share with you that your Mac has a SSH config
file in a .ssh
directory. The config
file is where you draw relations of your SSH keys to each GitHub (or Bitbucket) account, and all your SSH keys generated are saved into .ssh
directory by default. You can navigate to it by running cd ~/.ssh
within your terminal, open the config
file with any editor, and it should look something like this:
Host * AddKeysToAgent yes
> UseKeyChain yes
import { applyDecorators } from '@nestjs/common'; | |
import { ApiExtraModels, ApiQuery, getSchemaPath } from '@nestjs/swagger'; | |
/** | |
* Combines Swagger Decorators to create a description for `filters[name]=something` | |
* - has support for swagger | |
* - automatic transformation with nestjs | |
*/ | |
// eslint-disable-next-line @typescript-eslint/ban-types,@typescript-eslint/explicit-module-boundary-types | |
export function ApiFilterQuery(fieldName: string, filterDto: Function) { |
A collection of links to the excellent "Composing Software" series of medium stories by Eric Elliott.
# generate private key | |
openssl genrsa -out private.pem 2048 | |
# extatract public key from it | |
openssl rsa -in private.pem -pubout > public.pem |
{ | |
"name": "npm-scripts-example", | |
"version": "1.0.0", | |
"description": "npm scripts example", | |
"scripts": { | |
"prebuild": "echo I run before the build script", | |
"build": "cross-env NODE_ENV=production webpack", | |
"postbuild": "echo I run after the build script" | |
} | |
} |
Consider supporting my work by purchasing the course this tutorial is a part of i.e. VSCode Power User →
Local by FlyWheel
WordPress install is a custom installProxy cache passes GET instead of HEAD to upstream... so we have a 403.
This version include these fixes.