See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
<?php | |
/** | |
* Class RD_Text_Extraction | |
* | |
* Example usage: | |
* | |
* $response = RD_Text_Extraction::convert_to_text($path_to_valid_file); | |
* | |
* For PDF text extraction, this class requires the Smalot\PdfParser\Parser class. |
import Replicate from 'replicate' | |
import * as dotenv from 'dotenv' | |
dotenv.config() | |
const replicate = new Replicate({ | |
auth: process.env.REPLICATE_API_TOKEN, | |
}) | |
async function main() { | |
const training = await replicate.trainings.create( |
Warning Committing the .vscode files to your git repo should not be done, as configurations are not fully portable.
The file c_cpp_configuration.json
contains configurations for Nintendo 3DS, Switch, and Wii U. This helps with intellisense.
Create .vscode/c_cpp_configuration.json
in your project directory and then copy and paste the content as applicable.
This file was changed since it was uploaded to my GitHub repository to use the "env" JSON key. This is so more profiles can be easily created with defaults for each console and then adding extras, such as a debugging profile. On top of that, it was moved to a gist because they are much easier to update.
VMware vSphere 6 Enterprise Plus | |
1C20K-4Z214-H84U1-T92EP-92838 | |
1A2JU-DEH12-48460-CT956-AC84D | |
MC28R-4L006-484D1-VV8NK-C7R58 | |
5C6TK-4C39J-48E00-PH0XH-828Q4 | |
4A4X0-69HE3-M8548-6L1QK-1Y240 | |
VMware vSphere with Operations Management 6 Enterprise | |
4Y2NU-4Z301-085C8-M18EP-2K8M8 | |
1Y48R-0EJEK-084R0-GK9XM-23R52 |
import ts from 'typescript' | |
import { readFile, stat, unlink, writeFile } from 'fs/promises' | |
import * as path from 'path' | |
import { faker } from '@faker-js/faker' | |
interface Column { | |
columnType: string | |
default?: any | |
fakeMethod?: string // Optional custom faker method | |
} |
#!/usr/bin/env bash | |
sudo systemctl disable apparmor | |
sudo systemctl disable hassio-apparmor.service | |
sudo systemctl disable hassio-supervisor.service | |
sudo systemctl daemon-reload | |
sudo systemctl reset-failed | |
sudo rm /etc/systemd/system/hassio-supervisor.service | |
sudo rm /etc/systemd/system/hassio-apparmor.service |
Running your ASP.NET Core (or other) application in Docker using SSL should not be an overwhelming task. These steps should do the trick.
Run the following steps from a Linux terminal (I used WSL or WSL2 on Windows from the Windows Terminal).
It should look something like the content below; call it my-site.conf
or something like that.