Skip to content

Conversation

@duncanparkes
Copy link

It would be nice to be able to run minUP as a user which doesn't have write access to the directory with the code in (this is just good practice, and also, if it's a git checkout, it saves having to keep avoiding checking in data files).

This PR stops the dbname.txt file getting written to the code directory (I don't think this is used for anything, and doing it like it currently works stops you from running minUP as different users or running two minUP commands at once).

It also allows configuration of where the log files should go - the defaults should still be to the same place.

Cheers,

Duncan

@mattloose
Copy link
Member

Yep - great ideas. We will merge shortly.

@mattloose
Copy link
Member

This is still outstanding and will be resolved shortly.

I assume writing the dbname.txt file was debug that crept in
by accident.
@duncanparkes duncanparkes force-pushed the dont-write-in-code-directory branch from c4c4347 to 1b56293 Compare October 3, 2016 13:24
@duncanparkes
Copy link
Author

I've rebased this over master to save it going stale.

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.

2 participants