can a different sub directory folder name be used if I can not install in the root directory. http://yourname.com/phpgedview < The directions said to put phpgedview for the folder directory instead of the root itself.
Thanks
Sal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sal
For good file management, you should wish to install PGV into it's own directory, just like you would install any other program under the root in a separate directory. This keeps INDEX.html/php files from conflicting and allows easier management and removal or relocation.
Sure, I have multiple installations in a myriad of names: PGV3, PGV4, PGV424, PGV-423, roots, roots2, PGVtest, etc. All you need to do is direct your server to serve your desired installation from whatever domain or sub-domain name via the appropriate folder/directory. In other words, you can serve: http://mydomain.com from root/PGV4/ or root/PGV424/ or you can serve http://test.mydomain.com from root/PGVtest/ OR - any of these from a folder like /phpgedview/ not sure what difference it would make as to any naming unless you don't manage your DNS in this fashion and must direct people to a sub directory, like http://www.mydomain.com/www/phpgedview but this would be quite a rare configuration. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On my system, I have several different directories with different PGV installations in each, and I launch the version of PGV I want by mentioning its directory name following the web address. The main PGV installation is launched the same way, and that's the URL that's published and can be discovered through Google and several other legitimate search engines.
I have other applications in their own directories subordinate to webroot that are called up in a similar fashion.
The applications and PGV instances I launch this way appear and disappear as my needs change, so it's much simpler for me if I don't have to mess with server configurations too. The main, "production", instance of PGV doesn't change, of course.
When I upgrade PGV, I set up the new installation in a new directory, and when everything is working I simply change directory names to replace the old with the new. After that, the old installation becomes another instance of PGV that can disappear at will. You can use a similar technique if you need to temporarily remove PGV from public accessibility.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was wondering what the reason was for the sub directory installation.
can this be installed in the root directory. such as: http://yourname.com instead of http://yourname.com/phpgedview
can a different sub directory folder name be used if I can not install in the root directory. http://yourname.com/phpgedview < The directions said to put phpgedview for the folder directory instead of the root itself.
Thanks
Sal
Sal
For good file management, you should wish to install PGV into it's own directory, just like you would install any other program under the root in a separate directory. This keeps INDEX.html/php files from conflicting and allows easier management and removal or relocation.
Sure, I have multiple installations in a myriad of names: PGV3, PGV4, PGV424, PGV-423, roots, roots2, PGVtest, etc. All you need to do is direct your server to serve your desired installation from whatever domain or sub-domain name via the appropriate folder/directory. In other words, you can serve: http://mydomain.com from root/PGV4/ or root/PGV424/ or you can serve http://test.mydomain.com from root/PGVtest/ OR - any of these from a folder like /phpgedview/ not sure what difference it would make as to any naming unless you don't manage your DNS in this fashion and must direct people to a sub directory, like http://www.mydomain.com/www/phpgedview but this would be quite a rare configuration.
-Stephen
On my system, I have several different directories with different PGV installations in each, and I launch the version of PGV I want by mentioning its directory name following the web address. The main PGV installation is launched the same way, and that's the URL that's published and can be discovered through Google and several other legitimate search engines.
webroot/instance1 would be launched by http://mydomain.ca/instance1
webroot/instance2 would be launched by http://mydomain.ca/instance2
I have other applications in their own directories subordinate to webroot that are called up in a similar fashion.
The applications and PGV instances I launch this way appear and disappear as my needs change, so it's much simpler for me if I don't have to mess with server configurations too. The main, "production", instance of PGV doesn't change, of course.
When I upgrade PGV, I set up the new installation in a new directory, and when everything is working I simply change directory names to replace the old with the new. After that, the old installation becomes another instance of PGV that can disappear at will. You can use a similar technique if you need to temporarily remove PGV from public accessibility.
Stephen,
Thanks for the reply!
I am on a Godaddy severe and I never really messed with the dns before
I have changed the hosting redirect such as ns1.blabla.com
But never did a redirect to my own hosting account via the dns.
forgive me for but I never did this before.
I always created a redirect page that would send the site to the sub directory.
Can you give me a example of this
Thanks Sal
Thanks to you as well Canajun :)