saniyathossain

Important git notes

• Allow unrealted history to multiple repo

• git pull reponame branchname --allow-unrelated-histories

• https://stackoverflow.com/questions/37937984/git-refusing-to-merge-unrelated-histories-on-rebase

• Pushing to multiple repo

• http://caseyscarborough.com/blog/2013/08/25/pushing-to-multiple-remotes-using-git/

saniyathossain

const echoPostRequest = {
  url: 'https://<my url>.auth0.com/oauth/token',
  method: 'POST',
  header: 'Content-Type:application/json',
  body: {
    mode: 'application/json',
    raw: JSON.stringify(
        {
        	client_id:'<your client ID>',
        	client_secret:'<your client secret>',

saniyathossain

{
    "editor.fontFamily": "JetBrains Mono",
    "editor.fontSize": 15,
    "editor.fontLigatures": true,
    "files.trimTrailingWhitespace": true,
    "editor.wordWrap": "off",
    "editor.formatOnPaste": false,
    "editor.multiCursorModifier": "ctrlCmd",
    "editor.snippetSuggestions": "top",
    "editor.cursorStyle": "line-thin",

saniyathossain

<template>
    <table>
        <thead>
        <tr>
            <th v-for="column in parameters.columns" v-html="title(column)"></th>
        </tr>
        </thead>
        <tfoot v-if="footer">
        <tr>
            <th v-for="column in parameters.columns" v-html="column.footer"></th>

saniyathossain

<?php

namespace App\Providers;

use Illuminate\Support\Collection;
use Illuminate\Pagination\LengthAwarePaginator;

class AppServiceProvider extends ServiceProvider
{
    public function boot()

saniyathossain

<?php

namespace App\Eloquents\Traits;

use Illuminate\Database\Eloquent\Builder;
use Illuminate\Support\Str;
use ReflectionClass;

/**
 * Generates prefixed column along with padded specific model attribute (e.g. model table primary key attribute)

saniyathossain

FROM yourdockername/base-php-nginx:latest AS build
# BUILD STAGE
# the primary reason we have two build stages is so SSH key of private repo's will never
# be in final image

# COPY IN BUILD SSH KEY
# It won't be copied to final image
# add this build arg to compose file
ARG BUILDKEY
RUN if [ -z "$BUILDKEY" ]; then echo "BUILDKEY SSH NOT SET - ERROR"; exit 1; else : ; fi

saniyathossain

JetBrains Mono Font: Just a Programming Font
Ayu Theme: Theme for vscode
Docker: for view, run, inspect docker image, container, network, volume etc.
Bracket Pair Colorizer 2: for coloring bracket pairs for better visualization inside code 
File Utils: for sidebar enhancement -> (like duplicate file etc.. from left panel)
Editor Config: For editor configs
DotENV: for easier linting and syntax highlighting .env files
PHP Intellisense: This extension is very important for PHP lint, format, autocomplete class, Import class, go to class, method directly from code etc..
Inline Parameters for VSCode: optional: phpstorm like method argument highlighting
PHP Docblock: useful for adding method, class etc. top inline documentation

saniyathossain

Can I Remove MySQL Binary Log Yes, as long as the data is replicated to Slave server, it’s safe to remove the file. It’s recommend only remove MySQL Binary Log older than 1 month.

Besides, if Recovery of data is the main concern, it’s recommend to archive MySQL Binary Log.

There are several ways to remove or clean up MySQL Binary Log, it’s not recommend to clean up the file manually, manually means running the remove command.

Remove MySQL Binary Log with RESET MASTER Statement Reset Master statement is uses for new database start up during replication for Master and Slave server. This statement can be used to remove all Binary Log.

To clean up Binary Log on Master Server

saniyathossain

sudo update-locale LC_CTYPE=en_US.UTF-8;
sudo update-locale LC_NUMERIC=en_US.UTF-8;
sudo update-locale LC_TIME=en_US.UTF-8;
sudo update-locale LC_COLLATE=en_US.UTF-8
sudo update-locale LC_MONETARY=en_US.UTF-8;
sudo update-locale LC_MESSAGES=en_US.UTF-8
sudo update-locale LC_PAPER=en_US.UTF-8;
sudo update-locale LC_NAME=en_US.UTF-8;
sudo update-locale LC_ADDRESS=en_US.UTF-8;
sudo update-locale LC_TELEPHONE=en_US.UTF-8;