110 reputation
4
bio website
location
age 22
visits member for 11 months
seen Jun 16 at 10:45

Feb
26
comment Upgrade Apache 2.2.22 to 2.2.26 on Ubuntu 12.04 LTS
My configuration files have been in /etc/apache2/ because that is where Ubuntu installs Apache when installing from the repository. I was simply maintaining the location of Apache to reduce the number of variables changing. In any case, I'll keep playing around with it.
Feb
26
comment Upgrade Apache 2.2.22 to 2.2.26 on Ubuntu 12.04 LTS
I wouldn't say I blindly followed it. I instructed configure to prefix the path with the location of my previous apache2 installation. The configuration files are still there, and the sites are enabled. That said, even if they weren't, I theoretically still should've seen an "It works!" page, right?
Feb
26
asked Upgrade Apache 2.2.22 to 2.2.26 on Ubuntu 12.04 LTS
Feb
9
awarded  Supporter
Feb
9
accepted Setting up mail delivery to Django on Ubuntu
Feb
7
asked Setting up mail delivery to Django on Ubuntu
Jan
5
awarded  Scholar
Jan
5
comment Is it practical to use Google App Engine for a Django app?
Thanks, I really appreciate the input. Very helpful.
Jan
5
accepted Is it practical to use Google App Engine for a Django app?
Jan
5
asked Is it practical to use Google App Engine for a Django app?
Nov
29
awarded  Student
Sep
20
answered PHP thinks date.timezone isn't set
Sep
19
comment PHP thinks date.timezone isn't set
I did restart Apache, but I just solved it. For some reason there was a weird summation symbol before [PHP] on the first line of the file. I figured it was supposed to be there because it was in php.ini.default, but it works fine after removing it.
Sep
19
asked PHP thinks date.timezone isn't set
Jul
26
comment PIP not installing to virtualenv directory
Yes there is, and if I try to execute the python in that folder it successfully starts interactive python.
Jul
26
comment PIP not installing to virtualenv directory
I updated the question with the path. And I was originally trying that but it says "bad interpreter: No such file or directory". The other strange thing is even though I'm typing myenv.env/bin/pip, it is saying myenv.env/bin/python: bad interpreter
Jul
26
awarded  Editor
Jul
26
revised PIP not installing to virtualenv directory
added 118 characters in body
Jul
26
comment PIP not installing to virtualenv directory
I do see pip inside of myenv.env/bin/. I just tried "activating" my env again, and despite being in that mode, "which pip" and "which easy_install" both return "usr/local/bin/pip" and "usr/bin/easy_install" respectively.
Jul
26
comment PIP not installing to virtualenv directory
Same problem with other packages. And I believe easy_install requires sudo and would install into the global directory.