search

HumanDynamics / openPDS

openpds.media.mit.edu
MIT License
110 stars 33 forks source link

Is openPDS usable standalone? #10

Closed 0xdevalias closed 9 years ago

0xdevalias commented 9 years ago

I've been playing around with openPDS from this repo over the last few days, followed the instructions, hacked around with some things, read through parts of the source, etc and am still unable to get an instance running (or if I get it running, it's full of 500 server errors)

So I was wondering, is openPDS (as it exists publicly in this repo currently) actually runnable? I noticed a lot of internal references to Open Mustard Seed; will it only run within that environment?

I'd like to check it out/have a bit of a play (while I wait for access to OMS), but I don't want to waste more time on it if there's no chance of actually getting a local version running currently.

Would really appreciate some input/guidance on how to get it going if it can be :)

Thanks so much!!

brian717 commented 9 years ago

openPDS should be usable standalone (in conjunction with a registry server for authorization, though you can use the one at linkedpersonaldata.org if you'd rather not set up your own). References to OMS are outdated and from a time when openPDS was the personal data store component of that framework. openPDS has no dependencies on OMS. Documentation and namespaces have simply not been entirely updated yet.

0xdevalias commented 9 years ago

Fair enough, that makes sense. Does that mean it's no longer the PDS component of OMS?

I've tried setting openPDS up on Ubuntu 14.04, with some tweaking of the instructions I've managed to install the dependencies, setup the env sandbox, clone the repo, etc.

In configuration I changed the SQLite database to a path that exists, and I can't remember 100% but I think I changed (or tried to) the auth stuff to point to linkedpersonaldata.org

When I runserver it comes up, but then trying to load any page results in a 500 internal server error.

The first thing I noticed was a bunch of pages complaining about psycopg not being installed, which I could see was because it was commented out in requirements.txt Reenable that, but it complained further. Given I assume it's only needed if the DB is set to Postgres, I tried commenting out the import lines. I think that allowed it to get a little further, but still a 500 error (I believe it was talking about something databasey again, would have to double check)

Are you able to provide some information on specifically what parts need configuring on a custom install, and what I might of missed getting it going?

If I can manage to get things running I'm more than happy to contribute back my instructions, and probably a Vagrant and/or Dockerfile to make it way for others to install/try out :) — Sent from Mailbox

On Tue, Aug 26, 2014 at 3:03 AM, brian717 notifications@github.com wrote:

openPDS should be usable standalone (in conjunction with a registry server for authorization, though you can use the one at linkedpersonaldata.org if you'd rather not set up your own). References to OMS are outdated and from a time when openPDS was the personal data store component of that framework. openPDS has no dependencies on OMS. Documentation and namespaces have simply not been entirely updated yet.

Reply to this email directly or view it on GitHub: https://github.com/HumanDynamics/openPDS/issues/10#issuecomment-53292279

dazzaji commented 9 years ago

Hi all, Glad to see more instal/config activity. I wish I could assist technically. Let me know if something comes up that I can lend a hand with. Thanks,

On Mon, Aug 25, 2014 at 6:47 PM, alias1 notifications@github.com wrote:

Fair enough, that makes sense. Does that mean it's no longer the PDS component of OMS?

I've tried setting openPDS up on Ubuntu 14.04, with some tweaking of the instructions I've managed to install the dependencies, setup the env sandbox, clone the repo, etc.

In configuration I changed the SQLite database to a path that exists, and I can't remember 100% but I think I changed (or tried to) the auth stuff to point to linkedpersonaldata.org

When I runserver it comes up, but then trying to load any page results in a 500 internal server error.

The first thing I noticed was a bunch of pages complaining about psycopg not being installed, which I could see was because it was commented out in requirements.txt Reenable that, but it complained further. Given I assume it's only needed if the DB is set to Postgres, I tried commenting out the import lines. I think that allowed it to get a little further, but still a 500 error (I believe it was talking about something databasey again, would have to double check)

Are you able to provide some information on specifically what parts need configuring on a custom install, and what I might of missed getting it going?

If I can manage to get things running I'm more than happy to contribute back my instructions, and probably a Vagrant and/or Dockerfile to make it way for others to install/try out :) — Sent from Mailbox

On Tue, Aug 26, 2014 at 3:03 AM, brian717 notifications@github.com wrote:

openPDS should be usable standalone (in conjunction with a registry server for authorization, though you can use the one at linkedpersonaldata.org if you'd rather not set up your own). References to OMS are outdated and from a time when openPDS was the personal data store component of that framework. openPDS has no dependencies on OMS.

Documentation and namespaces have simply not been entirely updated yet.

Reply to this email directly or view it on GitHub: https://github.com/HumanDynamics/openPDS/issues/10#issuecomment-53292279

— Reply to this email directly or view it on GitHub https://github.com/HumanDynamics/openPDS/issues/10#issuecomment-53348196 .

brian717 commented 9 years ago

The Postgres dependency is recent and you're right - we are going to make that dependent on the backend you choose for the actual personal data (this is likely different from the Django ORM backend).

I can say that configuration changes are mostly in settings.py - pointing it to a working registry server, pointing the upload directory to one that exists (and that any web server process has read and write access to), and changing standard Django ORM settings.

Can you give more information about the 500 errors you're seeing? I'd love to help out. Also, are you using the Django debug server / Apache / something else?

RogerTangos commented 9 years ago

Hey @dazzaji - it's actually be really awesome if you'd ask technical questions about the system. We're working on the simplify branch right now and I'm trying to document and smooth over people's questions. So if you have any, please fire away!