You may find these commands useful when adjusting file and directory permissions.
To recursively chmod directories only:
find /your/site/root -type d -exec chmod 755 {} \;
To recursively chmod files only:
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
# test setting a guest environment variable based on a host environment variable | |
# if FOO_BAR is set locally, create command to add it to .profile in the guest | |
env_var_cmd = "" | |
if ENV['FOO_BAR'] | |
value = ENV['FOO_BAR'] | |
env_var_cmd = <<CMD |
#!/opt/local/bin/python | |
import httplib, json | |
APIKEY = "YOUR_API_KEY_HERE" | |
headers = {"TekSavvy-APIKey": APIKEY} | |
conn = httplib.HTTPSConnection("api.teksavvy.com") | |
conn.request('GET', '/web/Usage/UsageSummaryRecords?$filter=IsCurrent%20eq%20true', '', headers) | |
response = conn.getresponse() |
'use strict' | |
// A very simple nodeJS script that demonstrates how you can access | |
// memory usage information similar to how free -m works on the | |
// Raspberry Pi. Goes with µCast #14. http://youtu.be/EqyVlTP4R5M | |
// Usage: node pi_mem.js | |
// Example Output | |
// |
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.