figassis

figassis

[options]

#
# WARNING:
#  If you use the Odoo Database utility to change the master password be aware  
#  that the formatting of this file WILL be LOST! A copy of this file named
#  /etc/odoo/openerp-server.conf.template has been made in case this happens
#  Note that the copy does not have any first boot changes
#-----------------------------------------------------------------------------
#  Odoo Server Config File - TurnKey Linux

figassis

#!/bin/bash

if [[ "$1" != "" ]]; then
    S3BUCKETNAME="$1"
else
    echo ERROR: Failed to supply S3 bucket name
    exit 1
fi

aws s3 sync build s3://$S3BUCKETNAME --delete --cache-control max-age=31536000,public

figassis

AWS Route 53 white label nameserver setup

Also see: AWS CLI Setup

Links

• Route 53 introduction
• Official white label documentation
• CLI documentation

figassis

Proto3 Cheat Sheet

Information From: https://developers.google.com/protocol-buffers/docs/proto3

A few rules

• Declaring Message In Protocol Buffer:

• As you can see, each field in the message definition has a unique number.

• Field numbers identify fields in message binary format. Should not be changed once message is in use

figassis

#!/bin/bash
mkdir -p $HOME/go
curl -LO https://get.golang.org/$(uname)/go_installer && chmod +x go_installer && ./go_installer && rm go_installer
. ~/.bash_profile

echo "Go is installed and your GOPATH is '$HOME/go'"
echo "Please reload this shell or enter the command '. ~/.bash_profile'"

figassis

package main

import "fmt"

func main() {	
	slice := make([]int, 159)

	// Split the slice into batches of 20 items.
	batch := 20

figassis

Antígua e Barbuda - Antiguano
Argentina - Argentino
Bahamas - Bahamense
Barbados - Barbadiano, barbadense
Belize - Belizenho
Bolívia - Boliviano
Brasil - Brasileiro
Chile - Chileno
Colômbia - Colombiano
Costa Rica - Costarriquenho

figassis

<?
$entities = array('image', 'photo', 'text', 'source', 'site', 'traffic', 'money', 'book', 'e-book', 'file', 'smartphone', 'camera', 'notebook', 'cities', 'distances', 'cars', 'mobile', 'book', 'sex', 'love', 'classifieds', 'ads', 'alcohol', 'travel');
$verbs = array('sell', 'buy', 'rent', 'exchange', 'free', 'give', 'book', 'clean', 'find', 'classify', 'compare');
echo '<table style="width: 100%">';
foreach ($entities as $entity)
{
    echo '<tr>';
    foreach ($verbs as $verb)
        echo "<td style='font-size: 14px; padding: 5px; text-align: center'>$verb $entity</td>";
    echo '</tr>';

figassis

A few quick guidelines on my conventions when using Trello. These are not rules. Trello doesn't enforce a structure allowing each project to adapt to it's needs. But this is a good place to start:

Lists

• Unquoted - Any card being added to the project which is not in the statement of work and not a bug related to work covered by the statement of work goes here. The goal of this list is to avoid scope creep. If scope is being added we want it to be an explicit decision with an explicit cost estimation. The person creating the card should try to estimate the cost (or get someone to do so for them). The client can then choose to move it to the Todo list if they want to increase the scope. If they choose to hold off for now this list provides an excellent idea source for future rounds of development.
• Todo - These are tasks that need to be done which are not in active development.
• In Progress - These are tasks that are actively being worked on by a developer. If you are not actively w