]]>I compiled Apache 2.4.2 on CentOS 6.2 32 bit. I won’t detail here the installation process, if you need help just follow this tutorial.
The following instructions are based on the mod_auth_form documentation page and the few tutorials I found online.
First of all create a test folder in the web server root and put a test page inside it
1 2 3 4 | |
Then create a login page in the webserver root that will be used to authenticate users
1 2 3 4 5 6 7 8 9 10 11 12 | |
Please note that leaving the action empty, after a successfull login the user will be redirected to the previously requested resource.
Now edit Apache main configuration file enabling required modules
1 2 3 4 | |
and then add a Directory directive to protect the folder
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | |
Now add a user to the .htpasswd file and reload the web server configuration before trying to navigate to the protected folder.
1
| |
L’uomo oscilla tutta la vita fra il male e il bene, scivola, cade, si riarrampica, si pente, si ottenebra nuovamente, ma fino a che non ha varcato la soglia della malvagità il ritorno rimane nelle sue possibilità, ed egli resta nell’ambito delle nostre speranze. Quando invece, per la densità delle azioni malefiche, o il loro grado, o per il carattere assoluto del potere, egli oltrepassa d’un tratto la soglia, esorbita dall’umanità. Forse senza possibilità di ritorno.
[…]
Dobbiamo condannare pubblicamente l’IDEA stessa dello scempio compiuto da uomini sui loro simili. Tacendo sul vizio, ricacciandolo nel corpo perché non si riaffacci, noi lo SEMINIAMO, e in futuro germinerà moltiplicandosi per mille. Non punendo, non biasimando nepppure i malvagi, non ci limitiamo a proteggere la loro sterile vecchiaia, ma strappiamo da sotto alle nuove generazioni ogni fondamento di giustizia. Ecco perchè esse crescono “indifferenti”, non è colpa della “insufficiente educazione”. I giovani imparano che un’azione ignobile non viene mai punita sulla terra, anzi, porta sempre il benessere.
Non sarà accogliente un tale paese, farà paura viverci.
]]>Reacting well to competition requires critical analysis of your own product and its shortcomings, and a complete, open-minded understanding of why people might choose your competitors.
They’re not fanboys. They’re not brainwashed by “marketing”. Your competitors’ customers aren’t passing on your product because they’re stupid or irrational.
They’re choosing your competitors for good reasons, and denying the existence of such good reasons will only ensure that your product never overcomes them.
Permalink]]>In my opinion, the best computing model is one in which all the devices you use have operating systems, UIs, and interaction models that are appropriate for that device’s form factor and for its intended purpose with data being seamlessly shared between them. My interpretation of Windows 8 is that Microsoft tried to anticipate Apple combining their operating systems into one, and tried to beat them to it. However, I think they’ve beaten Apple to something Apple isn’t interested in doing, and that actually represents a big step backwards in computer interaction and productivity
Permalink]]>When you’re designing mobile interfaces, it’s best to make your targets big so that they’re easy for users to tap. But exactly how big should you make them to give the best ease of use to the majority of your users? Many mobile developers have wondered this, and most have turned to the user interface guidelines provided by the platform developer for the answer.
Permalink]]>
]]>Permalink]]>Calomel.org is a privately held site dedicated to documenting open source programs and configurations. The goal of our domain is to be simple to maintain, trivial to navigate and efficient to serve.
[…]
We do not accept any donations, gifts or financial reimbursement for information found on Calomel.org. This site is run for the sole purpose of sharing what we have learned with anyone who is interested. If you wish to contribute, please teach what you know to others and hopefully they will do the same. We all benefit from knowledge freely shared.
This tutorial assumes that you are using Debian 6 and the latest Mailman and Postfix stable versions and that you plan to use a dedicated subdomain for your lists.
Go to /etc/apache2/sites-available/ and create the file lists.mydomain.com with this content:
1 2 3 4 5 6 7 8 | |
Save the file and create the directories for public files and logs
1 2 | |
and enable the virtualhost:
1
| |
For Mailman and Postifx installation I followed the tutorial Manage Email Lists with GNU Mailman on Debian 6 (Squeeze) in the Linode Library.
Be sure to complete the Configure Virtual Hosting section before creating the default mailman list.
Now you need to tweak your subdomain configuration in order to access the mailman web interface. You can integrate your configuration using the sample file inside /var/lib/mailman/templates/apache.conf.
Below there’s the final configuration file:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 | |
To complete the configuration, add an index.html file to your subdomain root that forwards the requests to the mailman web interface
1 2 3 4 5 6 7 | |
When I completed the configuration I sent my first email to the list and got this error.
The error that the other server returned was:
550 550 5.1.1 <listname@lists.mydomain.com>:
Recipient address rejected: User unknown in local recipient table (state 14)
If you get this error probably the installation didn’t insert the corret aliases in the /etc/aliases file. To solve the problem just add this aliases to the file
mylist: "|/var/lib/mailman/mail/mailman post mylist"
mylist-admin: "|/var/lib/mailman/mail/mailman admin mylist"
mylist-bounces: "|/var/lib/mailman/mail/mailman bounces mylist"
mylist-confirm: "|/var/lib/mailman/mail/mailman confirm mylist"
mylist-join: "|/var/lib/mailman/mail/mailman join mylist"
mylist-leave: "|/var/lib/mailman/mail/mailman leave mylist"
mylist-owner: "|/var/lib/mailman/mail/mailman owner mylist"
mylist-request: "|/var/lib/mailman/mail/mailman request mylist"
mylist-subscribe: "|/var/lib/mailman/mail/mailman subscribe mylist"
mylist-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe mylist"
and run
newaliases
I followed the Theming & Customization instructions and modified only the ”custom” files beacuse I wanted to be able to upgrade Octopress without having to re-apply my changes every time.
Feel free to use the following code, just please give me credit and some backlink love.
First of all I changed the main layout width because I wanted the article content to be 640px wide, a populare image format, especially if you use Flickr.
I love the modern browser ability to resize images on the fly, but I prefer to keep my pages as light as possible, so I try to post images that fit the layout.
1 2 3 | |
Then I changed the default font and set it to Lato, including the font from Google Fonts
1 2 3 4 | |
1
| |
And finally I wrote my custom CSS. I use some external resource in my style:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 | |
Finally, even in discouraged, I used this function and I’m pretty satisfied.
1 2 3 4 5 6 7 | |
Look up HTML5, CSS3, etc features, know if they are ready for use, and if so find out how you should use them – with polyfills, fallbacks or as they are.
Permalink]]>
The Swan Lake performed by Sofia Ballet, end of the show. Teato Alighieri, Ravenna, Italy.
]]>I’ve been using it for the last two weeks and suddenly became my text editor of choice.
Permalink]]>I created a repository for the code and after the break you’ll find the instructions on how to set it up.
You’ll need some information to get started: first of all you need you Flickr username, with that you can obtain your Flickr user id using idgettr.
The last step is getting a Flickr API key that can be generated visiting this page: http://www.flickr.com/services/api/keys/.
When you are done, put these info in the _config.yml file:
1 2 3 4 | |
and then put the flickr.html file inside your Octopress installation in the directory source/_includes/custom/asides
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 | |
Now enable the aside in your _config.yml and you are done
1 2 3 4 5 6 7 | |
For a better result you should adjust the sidebar size to match the Flickr foto size. For example I set my sidebar size to 286px
1 2 | |
Yes, because what you are reading is pure and static old-school HTML, generated by Octopress on my iMac. And there’s more: everything is served by GitHub trought the Pages feature, completely free, but I’ll talk about this later.
Octopress is a framework built upon Jekyll, the Ruby static site generator that powers GitHub Pages.
Jekyll takes a content directory, parses all articles and pages through a Markdown converter and generates a static website that can be served with almost anything.
Octopress leverages all the power of Jekyll adding a great HTML5 template, mobile ready, and a lot of features like archives, an xml sitemap, code highlighting, external services integration (Twitter, Github, Google+), and much much more.
This solution makes your website really fast because there’s no dynamic code that runs on the server and no databases.
Now I can write articles using MarkDown and the beautiful iA Writer. Furthermore I can easily version my articles on GitHub and backup them using Dropbox.
One of my new year resolutions is to reduce costs for online services like webhosting, image hosting, backups, etc.
Having static html pages, I can host them on GitHub for free, while now I’m paying nearly 200$ every year for a linux/php/mysql hosting.
Maybe someday GitHub will start charging money for the hosting service, but for now I think is the best I can get.
Obviously I can’t host media files or archive on GitHub so I’ll use Flickr for image hosting and Amazon S3 for other files.
]]>If you are impatient and want to see the final result, this is a sceenshot of the search page.
In the previous post I used the standard method wp_dropdown_categories to get the categories list, now we need to generate a checkbox list instead of a dropdown list so we are going to build a custom method in the functions.php file:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | |
This method generates a list of categories with a checkbox for every category. The value of the checkbox is the category ID. Now we need to customize the search.php template adding a call to the function am_dropdown_categories:
1 2 3 4 5 6 7 8 9 | |
Notice that the checkboxes name is filterCat and that there’s an hidden cat field: this field is used by WordPress to apply the search category filter and accepts multiples values using the sintax cat=1,2,3 so we are going to add a Javascript function that populates the cat field using the proper formatting.
This JavaScript function is called before submitting the form and sets the cat field value concatenating all the selected checkboxes values into a single string. This function must be included in the page displayng the search form.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | |
The filter is now fully functional, but we need to customize the search result page to list the categories
Just add this code to the functions.php file
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | |
and call it in the search results page:
1 2 | |
That’s it.
]]>