Skip to content

Conversation

@thatandromeda
Copy link
Owner

I've made our docs more generally organized (separating dev and sysadmin docs, using complete sentences, stuff like that). As the person who has most recently needed project documentation, can you have a look and tell me if there are glaring omissions or inaccuracies? No need for in-depth wordsmithing - just want to put the docs on a more responsible footing.

@thatandromeda thatandromeda requested a review from gravesm February 5, 2018 21:01
@gravesm gravesm temporarily deployed to mitlibraries-hamlet-stag-pr-10 February 5, 2018 21:01 Inactive
@gravesm gravesm temporarily deployed to mitlibraries-hamlet-stag-pr-10 February 5, 2018 21:21 Inactive
@gravesm gravesm temporarily deployed to mitlibraries-hamlet-stag-pr-10 February 5, 2018 21:41 Inactive
@coveralls
Copy link

coveralls commented Feb 6, 2018

Coverage Status

Coverage increased (+50.5%) to 88.668% when pulling aee474a on 64_organize_docs into 21b9cac on master.

You only need the first three of these if you plan to be doing neural net training. If you're developing the Django parts you can skip them; just get a prebuilt neural net file (see below, "Neural net files").

### Other config
Postgres needs a database and user (default values are `hamlet` for database name and username, no password; override this if desired in `.env` with `DJANGO_DB`, `DJANGO_DB_USER`, `DJANGO_DB_PASSWORD`)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One suggestion would be to also add the ENGINE setting to .env. I'm actually running things locally with sqlite since it's easier to set up in dev. I'm running things with a custom setting file in order to do this, but would be nice to be able to skip that and put the config in .env.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea; done and documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants