Skip to content

Instantly share code, notes, and snippets.

@Neophen
Neophen / Essential Full-Stack Elixir - Phoenix Boilerplate Guide.md
Created November 6, 2024 05:41
Essential Full-Stack Elixir/Phoenix Boilerplate Guide

Essential Full-Stack Elixir/Phoenix Boilerplate Guide

Core Features

1. Authentication & Authorization 🔐

Complete user authentication system including signup, signin, password management, and session handling.

Common Requirements:

  • User registration and login
  • Password reset/recovery
@VideoCarp
VideoCarp / lexing.md
Last active March 31, 2026 12:29
Basics of lexing

Lexing for beginners

This is a guide that should teach you how to perform basic lexing in a functional programing language.
Everything was written in Elixir, but you should be able to follow it if you are using any functional programming language.
Or even an imperative programming language like Python, C or Java.\

What is lexing?

The first question you should ask yourself is, what is lexing? It's the same as tokenising, scanning or lexical analysis.
That might not help you if you haven't heard of these either. Put simply, lexing is the process of breaking down a string
into meaningful units, indepdendent of context.
What a lexer will do is make the following happen:

@Diasporism
Diasporism / redis_and_resque.mkd
Last active July 6, 2025 07:38
How to configure Redis and Resque for your Rails app.

Redis and Resque

What this guide will cover: the code you will need in order to include Redis and Resque in your Rails app, and the process of creating a background job with Resque.

What this guide will not cover: installing Ruby, Rails, or Redis.

Note: As of this writing I am still using Ruby 1.9.3p374, Rails 3.2.13, Redis 2.6.11, and Resque 1.24.1. I use SQLite in development and Postgres in production.

Background jobs are frustrating if you've never dealt with them before. Over the past few weeks I've had to incorporate Redis and Resque into my projects in various ways and every bit of progress I made was very painful. There are many 'gotchas' when it comes to background workers, and documentation tends to be outdated or scattered at best.