Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

symlink problem #13

Closed
ShoGinn opened this issue Jan 4, 2017 · 11 comments
Closed

symlink problem #13

ShoGinn opened this issue Jan 4, 2017 · 11 comments
Milestone

Comments

@ShoGinn
Copy link

ShoGinn commented Jan 4, 2017

So I keep all of my git items in the /opt folder and then symlink them to the root web directory.

because the user.php points to ../users.db its asking for rights to the /opt folder.

unless i move the repository to the root web directory it fails.

So traditionally i know that symlinks aren't a preferred practice but it has worked in the past ;)

@HeroCC
Copy link

HeroCC commented Jan 4, 2017

You can edit user.php to set where the DB goes.

@ShoGinn
Copy link
Author

ShoGinn commented Jan 4, 2017

@HeroCC I know you can modify it but the point is that if the version gets updated that file will get overwritten.

@causefx
Copy link
Owner

causefx commented Jan 4, 2017

can you just add www-data to the group that has permissions to opt?

@ShoGinn
Copy link
Author

ShoGinn commented Jan 4, 2017

@causefx I think for the purpose of the database files having them located elsewhere is necessary and configuring that is a good enhancement :)

@causefx
Copy link
Owner

causefx commented Jan 4, 2017

@ShoGinn correct, I was just speaking in the meantime.

@causefx causefx added this to the 1.0 milestone Jan 8, 2017
@causefx causefx mentioned this issue Jan 10, 2017
@hoopty
Copy link

hoopty commented Jan 12, 2017

@causefx, I would recommend that you have user.php include another (optional) config.php that can override the defaults you have there so folks can create/edit config.php with any server specific settings they need. Also, please put config.php in .gitignore so that updates and gut pulls, etc. do not ever need to touch it. Right now, we need to revert our customizations to users.php then get the latest & then re-appy those customizations.

@causefx
Copy link
Owner

causefx commented Jan 13, 2017

I'm already working on something similar to that for v1.0

When first installing it will ask you where you would like for it to store the database. It will then save it in an another file.

@causefx
Copy link
Owner

causefx commented Jan 15, 2017

just a heads up this is fixed.

@ShoGinn
Copy link
Author

ShoGinn commented Jan 15, 2017

Thanks! I have been trying to implement this into a simpler solution and integration into a nginx location setup!

@ShoGinn
Copy link
Author

ShoGinn commented Jan 15, 2017

so far I have:


   location ~ /(\.|users.db) {
        deny all;
    }

Any idea what you are going to do with that users folder??

@causefx
Copy link
Owner

causefx commented Jan 15, 2017

what ever location you specify on the startup when you update, will use that path for both the db file and users folder.

image

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

No branches or pull requests

4 participants