ismailmechbal

#!/usr/bin/env ruby
require 'net/http'
require 'json'


gitlab_token = "YOUR TOKEN"
gitlab_uri = "URL GITLAB"
# number of repositories to display in the list
# order the list by the numbers
ordered = true

ismailmechbal

require 'mandrill'
require 'json'

mandrill = Mandrill::API.new 'YOUR_API_KEY'

yesterday_number = 0
todays_number = 0

clock = Time.new
day = clock.day

ismailmechbal

Description

A Dashing widget that checks whether a server is responding to either an http or ping request. It displays either a check or alert depending on the response.

Usage

ismailmechbal

The MIT License (MIT)

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all

ismailmechbal

#!/bin/bash
# Dashing service
# Add this file to /etc/init.d/
# $ sudo cp dashboard /etc/init.d/
# Update variables DASHING_DIR, GEM_HOME, & PATH to suit your installation
# $ sudo nano /etc/init.d/dashboard
# Make executable
# $ sudo chmod 755 /etc/init.d/dashboard
# Update rc.d
# $ sudo update-rc.d dashboard defaults

ismailmechbal

# Nginx+Unicorn best-practices congifuration guide. Heartbleed fixed.
# We use latest stable nginx with fresh **openssl**, **zlib** and **pcre** dependencies.
# Some extra handy modules to use: --with-http_stub_status_module --with-http_gzip_static_module
#
# Deployment structure
#
# SERVER:
#  /etc/init.d/nginx                             (1. nginx)
#  /home/app/public_html/app_production/current  (Capistrano directory)
#

ismailmechbal

Adding an audit log to your Rails app

If you have any sort of administrative interface on your web site, you can easily imagine an intruder gaining access and mucking about. How do you know the extent of the damage? Adding an audit log to your app is one quick solution. An audit log should record a few things:

• controller entry points with parameter values
• permanent information about the user, like user_id
• transient information about the user, like IP and user_agent

Using the Rails framework, this is as simple as adding a before_action to your admin controllers. Here’s a basic version that I’m using in production.

ismailmechbal

Keybase proof

I hereby claim:

• I am ismailmechbal on github.
• I am unik (https://keybase.io/unik) on keybase.
• I have a public key whose fingerprint is 6AC0 C5C6 3427 5B42 6BCC 4570 1FB7 54F8 EBFA A377

To claim this, I am signing this object:

ismailmechbal

                        A D A M   D E R E W E C K I
1200 Sacramento St. Apt 405, San Francisco, CA 94108                740-502-3073
[email protected]                                           github.com/derwiki

               == P R O F E S S I O N A L   E X P E R I E N C E ==
CameraLends, Founder/CEO and Engineer (1/2013 - Present)
 * Hackers and Founders startup incubator participant
 * Tech stack: Rails 4.2/Bootstrap/jQuery/Heroku
 * Integrated: Facebook Login, Twitter, Twilio, Sift Science, Slack, Google
     Geocoder, Segment, Asana, Intercom, oLark, Zendesk

ismailmechbal

Rails naming conventions

General Ruby conventions

Class names are CamelCase.

Methods and variables are snake_case.

Methods with a ? suffix will return a boolean.