marnixk

/*
     ____  _        _              _   _ _   _ _
    / ___|| |_ _ __(_)_ __   ___  | | | | |_(_) |___
    \___ \| __| '__| | '_ \ / _ \ | | | | __| | / __|
     ___) | |_| |  | | |_) |  __/ | |_| | |_| | \__ \
    |____/ \__|_|  |_| .__/ \___|  \___/ \__|_|_|___/
                     |_|

    Purpose:

jordienr

// Remember to install mini-svg-data-uri
// Follow me on twitter for memes @jordienr

import { type Config } from "tailwindcss";
const {
  default: flattenColorPalette,
} = require("tailwindcss/lib/util/flattenColorPalette");
const svgToDataUri = require("mini-svg-data-uri");

export default {

ssrihari

An opinionated list of excellent Clojure learning materials

These resources (articles, books, and videos) are useful when you're starting to learn the language, or when you're learning a specific part of the language. This an opinionated list, no doubt. I've compiled this list from writing and teaching Clojure over the last 10 years.

• 🔴 Mandatory (for both beginners and intermediates)
• 🟩 For beginners
• 🟨 For intermediates

Table of contents

1. Getting into the language

wesort

Deployment

Creating and configuring a new site / environment occurs occasionally. Often, to update the underlying server software.

This site has been built with:

• Statamic v3 is a flat file CMS
• Statamic is a Laravel v9 package
• CSS via Tailwind v3
• Javascript via AlpineJS v3
• Composer is the PHP package manager
• NPM is the JS package manager

BjornDCode

// Source: https://twitter.com/calebporzio/status/1151876736931549185

<div class="flex">
    <aside class="h-screen sticky top-0">
        // Fixed Sidebar
    </aside>
    
    <main>
        // Content
    </main>

lukas-hetzenecker

import logging
import json

import google.oauth2.credentials
import time
from google.assistant.library import Assistant

from PyQt5.QtCore import pyqtProperty, pyqtSignal, pyqtSlot, QObject, QThread
from google.assistant.library.event import EventType

juliendargelos

// Usage:
//
// Get a Lorem Ipsum with 100 words (default):
// new LoremIpsum().string
// LoremIpsum.string
//
// Get a Lorem Ipsum with 200 words and without starting with "Lorem ipsum dolor sit amet...":
// new LoremIpsum({length: 200, classic: false}).string
// LoremIpsum.generate({length: 200, classic: false})
//

andreapavoni

Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.

For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai

kirkins

FROM alpine
MAINTAINER kirkins@gmail.com

# Checks if a port is open every 15 seconds

# Set the following variables
ENV WEBSITE google.com
ENV PORT 777
ENV PORT_DOWN_MSG 'Port is down send this message via email/text/ect'

athos

{:paths ["."]
 :deps {clansi/clansi {:mvn/version "1.0.0"}}}