yaikohi

@layer base {
  * {
    @apply border-border;
  }

  body {
    @apply bg-background text-foreground;
    font-feature-settings:
      "rlig" 1,
      "calt" 1;

huksley

MRSK

This documentation adds important additions to the docs for mrsk deploy tool (see github.com/mrsked/mrsk)

Destination flag

You can use mrsk deploy --destination staging

This will read config/deploy.yml and config/deploy.staging.yml files, and also will read .env.staging file if it exists.

huksley

# yaml-language-server: $schema=https://raw.githubusercontent.com/kjellberg/mrsk/validate-with-json-schema/lib/mrsk/configuration/schema.yaml
service: testexample
image: githubuser/test/main
servers:
  web:
    hosts: 
      - 1.1.1.1
    labels:
      traefik.http.routers.web.rule: Host(`test.example.com`)
      traefik.http.routers.web_secure.entrypoints: websecure

nymous

Logging setup for FastAPI

This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.

Then, you can use Structlog loggers or standard logging loggers, and they both will be processed by the Structlog pipeline (see the hello() endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!

Requests are assigned a correlation ID with the asgi-correlation-id middleware (either captured from incoming request or generated on the fly). All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented. This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog. You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom

axeldelafosse

// DEPRECATED

const {
  withDangerousMod,
  WarningAggregator,
  AndroidConfig,
  withAppBuildGradle,
} = require("@expo/config-plugins");
const path = require("path");
const fs = require("fs");

GregBrimble

import Image, { ImageLoader } from "next/image";

type Width = [string, number];

const widths = {
  sm: 640,
  md: 768,
  lg: 1024,
  xl: 1280,
};

j-bullard

import "./styles.css";
import { Person } from "./types";
import { Listbox } from "./listbox/listbox";
import { useForm } from "react-hook-form";

const people: Person[] = [
  { id: 1, name: "Durward Reynolds", unavailable: false },
  { id: 2, name: "Kenton Towne", unavailable: false },
  { id: 3, name: "Therese Wunsch", unavailable: false },
  { id: 4, name: "Benedict Kessler", unavailable: true },

0xced

platform :ios, '12.0'

target 'MyApp' do
  inhibit_all_warnings!
  pod 'libextobjc/EXTKeyPathCoding', '0.6'
  pod 'libextobjc/EXTScope',         '0.6'
  pod 'Mantle',                      '~> 2.1'
  pod 'RSParser',                    :git => 'https://github.com/0xced/RSParser', :branch => 'nsarray'
end

DimosthenisK

import { SetMetadata } from '@nestjs/common';

export interface SelfDecoratorParams {
    userIDParam: string;
    allowAdmins?: boolean;
}

export const Self = (params: SelfDecoratorParams | string) =>
    SetMetadata(
        'selfParams',

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default