The goal of this cheatsheet is to make it easy to add hand-rolled authentication to any rails app in a series of layers.
First the simplest/core layers, then optional layers depending on which features/functionality you want.
Specs |
|
|---|---|
| AUTHOR | Ira Herman |
| LANGUAGE/STACK | Ruby on Rails Version 4, 5, or 6 |
| ## | |
| # Program to help you hack terminals in Fallout | |
| # | |
| # Usage: | |
| # | |
| # Run the program once with a list of words in the terminal. The program will | |
| # output a list, and the first word in the list is the word you should pick | |
| # because it will eliminate the most possibilities. | |
| # | |
| # If that word is incorrect, then re-run the program with two lists, first the |
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
The game we're building is a simple side-scrolling racing game. The player's car is static on the screen, only the background is moving. The enemies are planes whom the player must dodge using the up and down arrow keys. If the player hits a plane, he dies. One point is given each time a plane goes off screen without touching the player.
Our game is composed of sprites. Each sprite has a position (x, y), velocity (speed) and one image, or more if animated.
Images are loaded from the DOM using their CSS selector (imagesSelector). We use ID selectors (#name) for single images and class selectors (.name) for animated sprites composed of several images.
See the images used in the game.
I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
| gem 'kaminari' | |
| gem 'ransack' |
Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.
Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.
First you will need to get an OAuth Token from GitHub using your own username and "note"
| # inspired by https://mriet.wordpress.com/2012/07/01/merge-bubbles-are-bad/ | |
| # and http://snipplr.com/view/26715/ | |
| # 1. first rebase all your local commits into one commit, e.g. for the last 3 commits into one you can use | |
| git rebase -i HEAD~3 | |
| # and 'pick' the first, 'squash' the other commits | |
| # 2. check the commit's sha id and save it somewhere |
| <% flash.each do |type, message| %> | |
| <div class="alert <%= bootstrap_class_for(type) %> fade in"> | |
| <button class="close" data-dismiss="alert">×</button> | |
| <%= message %> | |
| </div> | |
| <% end %> |
Vou iniciar este post com uma breve visão do que EU entendo sobre os principais XDD para em seguida discutir o motivo pelo qual não os acho relevante. Gostaria também de ressaltar que posso SIM ter uma visão limitada ou equivocada destes XDD’s, porém não vamos minimizar esta discussão com argumentos simplórios como “falta de conhecimento”, “falta de prática” ou coisas do gênero... pois o que será discutido aqui é um pouco mais conceitual e filosófico do que as técnicas/processos em si.
Com isso dito, vamos lá:
Esta técnica (ou processo) que visa obter uma maior qualidade na arquitetura/código, pois guindo o desenvolvimento por testes além de se ter um resultado mais assertivo, você também obtém uma arquitetura desacoplada. Geralmente se aplica este processo (NovoTeste->Falha->Implantação->Sucesso->NovoTeste...) em pequenos ciclos.