aaronbushnell

📦 Installation

1. Run composer require omnilight/yii2-scheduling to install the scheduling package
2. Setup a config/schedule.php file to house your scheduled processes
3. Modify your config/app.php to include the schedule component details to run the Craft command (instead of yii)
4. Run php craft schedule/run --scheduleFile=@config/schedule.php to process any scheduled operations.

💡 Tip: You likely want to run php craft schedule/run --scheduleFile=@config/schedule.php on a cron job that fires every minute!

🙏 Credits

samhernandez

<?php

use craft\base\Element;
use craft\db\Query;
use craft\db\Table;
use craft\elements\Asset;
use craft\elements\Entry;
use craft\errors\ImageException;
use craft\helpers\Assets;
use craft\helpers\FileHelper;

jeromecoupe

name: Craft CMS deployments

on:
  push:
    branches: [master]

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest

KatieMFritz

Craft 3 plugins for better author experience

Annotated Notes: For admin notes with automatic timestamps.

Control Panel Body Classes: Add body classes to various Control Panel screens for easier styling (in combination with Control Panel CSS).

Control Panel CSS: To make style tweaks to the control panel. See web/cp.css for styles.

Control Panel Nav: Custom navigation menus for each user type, for easier navigation.

johannaratliff

Context

This is for programmers who want to ramp on Go, without resources that reiterate programming fundamentals. This would not be a good list of resources for folks who are learning to program using Go as their first language. Some resources that I dismiss here would be super valuable for newer folks. This is a selection of resources for those who understand programming fundamentals in a different language already.

Advice

1. First steps = Tour of Go
2. Don't waste time on Go Fundamentals-type books - it all lives in tour of Go.
3. Consider joining the Gophers Slack
4. When you need help, the Go Playground allows you make a quick scratch file and share it. Others trying to help can run your code easily this way.

piotrpog

{# v2 #}

{% macro url(routeName, tokens) %}
{% spaceless %}
{% set keyword = 'name' %}
{% set routeString = null %}
{% for route, routeSettings in craft.app.routes.getConfigFileRoutes %}
    {% if routeSettings[keyword] is defined and routeSettings[keyword] == routeName %}
    {% set routeString = route %}
    {% endif %}

ostark

class EventCatcher
{

    /**
     * @var array 
     */
    protected $classConstants = [];

    public function __invoke(yii\base\Event $event)
    {

gricard

If you enjoyed reading this, I'm intending to do more blogging like this over here: https://cdgd.tech

This is not a complaint about Webpack or v4 in any way. This is just a record of my process trying it out so I could provide feedback to the webpack team

Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it. All I need to do is npm i -D webpack@next, right?

+ webpack@4.0.0-beta.2

cham11ng

A Relatively Secure Server Stack Setup in Ubuntu 16.04 LTS

Anup Dhakal

Sagar Chamling

Introduction

In this guide, LEPP stands for Linux, Nginx (pronounced as Engine-X) , Postgres and PHP (PHP Hypertext Preprocessor).

threequal

Newsletters

In no particular order

• Versioning
• Sidebar.io
• CSS Tricks
• Smashing Magazine
• Front End Front
• JavaScript Weekly