Skip to content

Instantly share code, notes, and snippets.

View christophermoura's full-sized avatar

Christopher Moura christophermoura

View GitHub Profile
@christophermoura
christophermoura / latin-to-ascii.js
Created November 1, 2023 18:26 — forked from adarshpastakia/latin-to-ascii.js
Latin characters to ASCII Conversion
export function getAscii(str) {
var conversions = new Object();
conversions['ae'] = 'ä|æ|ǽ';
conversions['oe'] = 'ö|œ';
conversions['ue'] = 'ü';
conversions['Ae'] = 'Ä';
conversions['Ue'] = 'Ü';
conversions['Oe'] = 'Ö';
conversions['A'] = 'À|Á|Â|Ã|Ä|Å|Ǻ|Ā|Ă|Ą|Ǎ';
conversions['a'] = 'à|á|â|ã|å|ǻ|ā|ă|ą|ǎ|ª';
@christophermoura
christophermoura / 55-bytes-of-css.md
Created October 3, 2022 10:09 — forked from JoeyBurzynski/55-bytes-of-css.md
58 bytes of css to look great nearly everywhere

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}
@christophermoura
christophermoura / python-guide.sh
Last active July 19, 2021 20:38 — forked from henriquebastos/python-guide.sh
The definitive guide to setup my Python workspace
# The definitive guide to setup my Python workspace
# Author: Henrique Bastos <henrique@bastos.net>
# Updated to use zsh and Python 3.9.2
PY3=3.9.2
PY2=2.7.16
PY3TOOLS="youtube-dl s3cmd fabric pytest"
PY2TOOLS="rename mercurial"
VENVS=~/.ve
@christophermoura
christophermoura / README.md
Created November 15, 2019 11:08 — forked from zenorocha/README.md
A template for Github READMEs (Markdown) + Sublime Snippet

Project Name

TODO: Write a project description

Installation

TODO: Describe the installation process

Usage

@christophermoura
christophermoura / README-Template.md
Created January 9, 2019 15:27 — forked from PurpleBooth/README-Template.md
A template to make good README.md

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

@christophermoura
christophermoura / change-favicon.js
Created October 8, 2018 04:52 — forked from mathiasbynens/change-favicon.js
Dynamically changing favicons with JavaScript
/*!
* Dynamically changing favicons with JavaScript
* Works in all A-grade browsers except Safari and Internet Explorer
* Demo: http://mathiasbynens.be/demo/dynamic-favicons
*/
// HTML5™, baby! http://mathiasbynens.be/notes/document-head
document.head || (document.head = document.getElementsByTagName('head')[0]);
function changeFavicon(src) {
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<opml version="1.0">
<head>
<title>Pocket Casts Feeds</title>
</head>
<body>
<outline text="feeds">
<outline xmlUrl="http://feeds.feedburner.com/braincastmp3" type="rss" text="Braincast" />
<outline xmlUrl="https://hipsters.tech/feed/podcast/" type="rss" text="Hipsters Ponto Tech" />
<outline xmlUrl="Http://feeds.feedburner.com/frangofinopodcast" type="rss" text="Frango Fino" />
@christophermoura
christophermoura / GitHub-Forking.md
Created November 3, 2017 00:51 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
export WORKON_HOME=~/.envs
export PROJECT_HOME=~/Documentos/pythonprojects
export PATH=$HOME/.bin:$PATH
eval "$(pyenv init -)"
pyenv virtualenvwrapper_lazy
alias deploygithub='git push -u --force origin master'
alias deployheroku='git push -u --force heroku master'