Hazuli Fidastian hazulifidastian

Step 1: SSH Daemon

In your WSL instance, re-install OpenSSH server as follows.

sudo apt remove --purge openssh-server
sudo apt install openssh-server

Edit /etc/ssh/sshd_config (e.g. sudo vi /etc/ssh/sshd_config) and add the following lines to the bottom of the file. Ensure you replace WSL_ACCOUNT_NAME with your WSL2 account name.

after Build 17093

can override settings by edit "/etc/wsl.conf"
normally this file is not exists at first

$ sudo vi /etc/wsl.conf

[interop]
appendWindowsPath = false

Open File App\Providers\AppServiceProvider

Change method boot

use Carbon\Carbon;


public function boot()
{
	config(['app.locale' =&gt; 'id']);

Merged from https://github.com/joelparkerhenderson/git_commit_message and https://chris.beams.io/posts/git-commit/

General Rules

Commit messages must have a subject line and may have body copy. These must be separated by a blank line.
The subject line must not exceed 50 characters
The subject line should be capitalized and must not end in a period
The subject line must be written in imperative mood (Fix, not Fixed / Fixes etc.)
The body copy must be wrapped at 72 columns
The body copy must only contain explanations as to what and why, never how. The latter belongs in documentation and implementation.

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

Goals
Proposal
- Commit Message Format

Allowed ``

	/**
	* A Javascript module to loadeding/refreshing options of a select2 list box using ajax based on selection of another select2 list box.
	*
	* @url : https://gist.github.com/ajaxray/187e7c9a00666a7ffff52a8a69b8bf31
	* @auther : Anis Uddin Ahmad <[email protected]>
	*
	* Live demo - https://codepen.io/ajaxray/full/oBPbQe/
	* w: http://ajaxray.com \| t: @ajaxray
	*/
	var Select2Cascade = ( function(window, $) {

	# === Optimized my.cnf configuration for MySQL/MariaDB (on Ubuntu, CentOS, Almalinux etc. servers) ===
	#
	# by Fotis Evangelou, developer of Engintron (engintron.com)
	#
	# ~ Updated September 2024 ~
	#
	#
	# The settings provided below are a starting point for a 8-16 GB RAM server with 4-8 CPU cores.
	# If you have different resources available you should adjust accordingly to save CPU, RAM & disk I/O usage.
	#