-

So true.
(Source: cunexttewsday, via lxghtxnxngbxlt)
-
https://www.facebook.com/pages/Pollo-Olivera-Portraits-Lifestyle/134607333360040?ref=tn_tnmn
-

Ya quisieran las mias tener rayos
(Source: gabeeintheskywithdiamonds)
-
Getting “Symbolic link not allowed or link target not accessible” while configuring Apache?
Reconfiguring my dev environment, I decided to change the location of my local web server directories, from /var/www to ~/, so that I could just backup my Home folder, and I’d only need to set some symbolic links when restoring or reinstalling my OS.
The problem arised when I did in fact move all to ~/, configured symbolic links, and I was still getting “Symbolic link not allowed or link target not accessible” in my Apache 2 logs.
Long story short, I had to add execute permission to /home/lobo to www-data user. That allows the os to CD to /home/lobo/mysite. So:
chown :www-data /home/lobo
chmod g+x /home/lobo
That did the trick!
Edit:
The fact is that you need permission to CD to the whole path. Doing sudo su www-data and cd’ing /home then /home/lobo throwed the error, then added the necessary permissions to “lobo” and finally inner folders so that Apache could work with them (755 to all directories and below works).
-
byobu (screen) stopped working. Here’s how I solved it!
My byobu was working ok until a couple of days.
it closed the very second i started it, saying [screen is terminating].
I had to remove it since it didn’t allow me to use my terminals.
Steps to solve my situation:
- add to “/etc/fstab” this line: “none /dev/pts devpts defaults 0 0”
- reboot
- open byobu (or screen)
- a page that made me press return or space to continue appeared. Apparently, this was stoping byobu from working.
- removed the line added in step 1
- reboot
- now we are working again, with byobu
This page helped me to know which command to use: http://forum.slicehost.com/index.php?p=/discussion/2577/screen-no-more-ptys/p1
The fact that a confirmation “screen” appeared after starting byobu, made me think of this halting byobu on the first time.
-
Running “good citizen” Yii Console Commands
When you run a website, that has commands running using cron, you should run your commands as the same user as your website (ex: apache, www-data).
Here’s a simple how-to:
- give access to www-data to execute yiic
- run yiic through /etc/crontab, not via “root“‘s crontab (the one you configure running crontab -e). This /etc/crontab has a new column for the username, so you can run commands via www-data
my /etc/crontab says:
*/1 * * * * www-data /bin/scripts/sendMail.sh> /dev/null
Of course, you have to give access to www-data to run sendMail.sh
-
Adding CSS prefixer to the toolbox
Now I just want all browser specific prefixes to be added automatically on my compilelesscss shell script.
This can be done thanks to the work done by http://cssprefixer.appspot.com/
You can run it from the web (not very usable), or just run: sudo pip install —upgrade cssprefixer
Now you can run cssprefixer yourcssfile.css >newcssfilewithprefixes.css
Done!
-
How to solve “The following packages have been kept back: libmysqlclient16”
I have been getting this msg from my linux apt-get upgrade.
After researching, it was caused by having mysql-workbench-gpl, that apparently installs mysqlclient, and having percona-mysql installed.
Running
aptitude upgrade —full-resolver
offered me choices: remove mysql-workbench-gpl, or percona.
I removed mysql-workbench-gpl, thus, upgraded percona, and later reinstalled mysql-workbench-gpl.
Now we are all happy again :)
-
How to install LessCSS using Node sources (Ubuntu Linux)
$ git clone https://github.com/joyent/node node
$ cd node
$ ./configure
$ make
$ sudo make install
$ npm install less
$ sudo ln -s ~/.npm/less/1.3.0/package/bin/lessc /usr/bin/lessc
(1.3.0 is the current version number. replace with yours)
lessc up and running!
-
as always, RHCP a source of inspiration
–
