Difficulty with the install

[Ashkeelun]

So I've been trying for a while now and have had a lot of problems getting it installed on my computer.

First it docker isn't compatible with Windows Home edition, so I got Windows Pro installed and then I ran into this error:

I read through your documentation but didn't find any manual installation instructions. If I could get a list of all the python dependencies I think I could manage it with a bit of work but at this point I'm kind of dead in the water as my current computer doesn't really support virtualization.

[bparish628]

Take a look at Other Installation. It's not in master yet (still in dev), but that is how to install everything locally.

[Ashkeelun]

I have successfully made it this far in the full install doc

When I run these initial migrations should I get a CommandError?

[bparish628]

I don't actually think you have to do that 😬 . Try just running a python manage.py migrate.

[Ashkeelun]

Okay it looks like that worked. does the test use a different database from msr14?

[bparish628]

@jakeharding would know better, but from my understanding it creates a test database with the same settings from local_settings.py (with _test appended). Is your local_settings.py setup?

[jakeharding]

You will need to setup a test database for the tests as covered in the readme.

[Ashkeelun]

Yeah I don't think the user has access to do that but I could create the database

[germonprez]

You may be able to use

opendata.missouri.edu User msr Pass ghtorrent DB msr

On Apr 14, 2017 12:09 PM, "Chris Bane" notifications@github.com wrote:

Yeah I don't think the user has access to do that but I could create the database

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jakeharding/repo-health/issues/56#issuecomment-294193254, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoDUJc5z2sLE7_OzhCwIUTE4k0fS8ZFks5rv6hYgaJpZM4M91Ot .

[jakeharding]

I am not sure what you mean by the user doesn't have access but you create another database in the fashion as you did for production but prepend the name with 'test_'.

[Ashkeelun]

I tried creating a test_msr14 schema that was still referencing the msr14 shema so I changed the local_settings.py to the test_msr14 database. It complained that there were no tables so I ran all the migrations then it still errored out so I tries changing settings to use the database that @germonprez provided above and I got the same error I was getting before which was this.

I've spent over 15 hours trying different things to get this to run on my hardware.

Also I began reading down further, is the npm start a node.js server?

[jakeharding]

Not exactly. You will need to create a whole new database for testing and populate it with same data as your production database. You will not need to make any changes to your local settings because Django will look for a database named with test_ followed by you database name in the local settings.

[Ashkeelun]

I've tried, this is what I get.

[jakeharding]

Normally the host is set to local host. Does the dev server start when you run manage.py runserver?

[Ashkeelun]

yes

here I recreated test_msr14

[jakeharding]

It looks like the connection is made but no tables have been created. Are you able to view data in the test database in your mysql workbench?

[Ashkeelun]

Yes

[jakeharding]

Those are all of the Django tables but none of the msr14 tables. You will need to run msr14 SQL script to create the tables and insert the data.

[jakeharding]

@Ashkeelun Any luck?

[Ashkeelun]

heh.. no I'm not really sure where that script is located. I couldn't find it in you're repo, and the computer I had got everything setup for this is at my work, and I went home for the day.

[jakeharding]

You will have to download it from ghtorrent and unpack it. The link is in the readme.