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

Installing in subdir doesn't work #24

Open
pietercolpaert opened this issue Jul 29, 2013 · 4 comments
Open

Installing in subdir doesn't work #24

pietercolpaert opened this issue Jul 29, 2013 · 4 comments

Comments

@pietercolpaert
Copy link
Member

I have tried to install it in a subdir but that didn't work: it instead went straight for the document root.

@benjaminmestdagh
Copy link
Member

The installer always installs the DataTank in the parent directory of the directory the installer is in. So, if you want the DataTank in a subdir, you have to create that directory, put the installer's directory in it, and then run the installer from there (this is mentioned in the readme).
Perhaps you have been trying to change the DataTank's directory from within the installer by changing the 'subdir' setting, but that won't physically change the location of the DataTank installation, it will only change the setting in the config file. As the information button next to this setting states, you should only change it if you plan on using a virtualhost, or if you want to move the DataTank directory to a different location after the installation.

@pietercolpaert
Copy link
Member Author

Oh! If this wasn't clear to me, it won't be clear to anyone else either I guess...

Based on the url in the address bar we can also do a very good guess about the hostname/subdir, right? At this moment it gives something with "public" in it.

@benjaminmestdagh
Copy link
Member

It was indeed very confusing, so I changed the name of the setting in the installer to 'Public directory', as that is what the setting is for (the 'subdir' name is the name of the setting in the DT config file). That also makes more clear why the 'public' part is added to the directory: it points to the public directory of the DT installation. (the subdir is already guessed; the "public" part is added deliberately)

@coreation
Copy link

👍 !!

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

No branches or pull requests

3 participants