Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In the directory <code>/home/user/example.com</code> you need to add a symlink to your database file too.</p> <p>Also:</p> <ul> <li>You only need to append <code>/home/user/example.com/project</code> to the path. The other two are not necessary, though they should not cause problems.</li> <li><p>Instead of hardcoding the path <code>/home/user/example.com/project</code> you can use <code>os.getcwd()</code>:</p> <pre><code>sys.path.append(os.path.join(os.getcwd(), 'project')) </code></pre></li> </ul> <p>After you make changes to this file or other files in your project, don't forget to do <code>touch tmp/restart.txt</code> to notify Passenger.</p> <p>By the way, at the moment Django works with Python versions 2.6.5 to 2.7 with experimental support for 3.2 and 3.3. According to the <a href="http://wiki.dreamhost.com/Python" rel="nofollow">Python wiki</a> on DreamHost, most servers should be using Python 2.6.6 as of February 2012, except <em>some</em> servers. Check your version of Python with <code>python --version</code> and if it's not 2.6.6 then you can ask the support team to upgrade it on your server.</p> <p>I tried using Django with Python 3.2 or 3.3 on DreamHost but it's problematic. It doesn't work with 3.2 because the <code>mod_wsgi</code> module of Apache does not seem to work with this version at the moment. It could work if you install it from source, but being a shared hosting, we don't have control over that. I don't know for sure but if <code>mod_wsgi</code> doesn't work with 3.2 then it won't work with 3.3 either. So I think it's best to stick to a supported version of 2.x version if you want to use Django on Dreamhost.</p>
    singulars
    1. This table or related slice is empty.
    1. PODjango: 500 internal server error with Passenger on Dreamhost
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjanos
    1. USjanos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODjango: 500 internal server error with Passenger on Dreamhost
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks but it didn't work too. Maybe I should rollback to django 1.4
      singulars
      1. PO
      1. USFiras
    2. COI updated my answer. It has to work, so don't give up!
      singulars
      1. PO
      1. USjanos
    3. COAaaaaaaaaaand it worked ! My server has Python 2.6.6 so i just created a new virtualenv with it, moved my project, changed the INTERP path in passenger to python 2.6.6, restarted DH, and it finally worked. Thanks a lot Janos, this really helped me because i thought the problem was on the passenger side and i would never have thought about switching to another python version.
      singulars
      1. PO
      1. USFiras
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload