search

FinalsClub / karmaworld

KarmaNotes.org v3.0
GNU Affero General Public License v3.0
7 stars 6 forks source link

virtual machine doesn't handle secret directory correctly #300

Closed btbonval closed 10 years ago

btbonval commented 10 years ago

VM fails to set permissions on the secret directory after importing it through Vagrant.

I saw this in the output:

chown: cannot access `karmaworld/secret/*.py': No such file or directory

In the directory, one file is being missed (the one that the Vagrant file generates), and is owned by root:root instead of vagrant:vagrant:

vagrant@vagrant-ubuntu-precise-32:~/karmaworld$ ls -l karmaworld/secret/
...
-rw-r--r-- 1 root    root     219 Jan 23 06:56 db_settings.py
...
btbonval commented 10 years ago

For reference, this area of the Vagrant file: https://github.com/FinalsClub/karmaworld/blob/594944c087b7cddc23323521a1ad716e842ca5d9/Vagrantfile#L65-L81

btbonval commented 10 years ago

hrm. I'm going to go ahead and guess the path differences are the problem: karmaworld/$SECRETPATH/ (correct) vs $SECRETPATH/*.py (incorrect).

Probably need to change this to be karmaworld/$SECRETPATH/*.py: https://github.com/FinalsClub/karmaworld/blob/594944c087b7cddc23323521a1ad716e842ca5d9/Vagrantfile#L81

btbonval commented 10 years ago

That worked.