• Check that only your webroot directory is publicly visible, and that your secrets (such as your app salt, and any security keys) are private and unique as well
Among CakePHP deployment guide is this^^^, that mean point mydomain.com to this DIR webroot … or…?
The relative urls should work then?
Firstly, no offense, but this question is not clear enough to be really understood and answered effectively, at least in my opinion. I’ll take a stab though.
If what you’re asking is what that quote means, it means that you need to point mydomain.com at your app’s webroot directory, and that the other folders are not publicly visible (file permissions, etc) and that your secrets are also somewhere not publicly accessible and unique to this specific CakePHP app.
And yes, relative urls should work if the app is set up properly.
The dir domain points to and documentroot of site are or can be different?
Surely if you have been a domain registrar since 1998 you should already know all this - and if that domain isn’t yours then why are you referencing that instead of your domain or the placeholder - example.com
Surely it could be just as simple that he used mydomain.com as a placeholder and didn’t use example.com? Why would one assume that it isn’t a placeholder, I see plenty of clues to suggest it likely is.
Maybe stop taking things so literally and actually try to provide assistance if you are going to post a reply.
@lsepolis123, did that answer your question, as I believe CakePHP is simply suggesting you need to setup the configuration properly for your application. The public folder needs to be where you want it, be it the root of the domain or a folder within it, and your configuration files should reflect that but be stored in a non-publically accessible location.
Because it is a real domain and example.com is assigned for use as a placeholder when you need one.
If people advertise other people’s sites instead of using the correct placeholder then they need to be advised that there is an actual domain assigned for use as a placeholder - example.com
That may be, but your post barely did that 
Might want to think of a better way of stating that next time 
Hopefully my second post cleared that up.
If it didn’t then the following will:
There is a domain specifically assigned for use as a placeholder - example.com - that you should use when you don’t want to specify your real domain. You should always specify either your real domain or example.com when specifying a domain name as if you use anything else you are giving someone else’s domain name and both advertising their site and asking how to solve your problem on their site.
All of the most obvious values I have seen people attempt to use as placeholders are real sites that are long established and which most likely don’t have the problem you want fixed.
This is placeholder.
How in cpanel and plesk set the:
Public access folder
Non public access folder
If example.com domain point to /gallery/… and having and others domains point to other folders…not related…well?
If you are using cpanel, anything outside the public_html folder is “secret” and can’t be accessed unless you point to them.
You use the Addon Domains option in cPanel to point different domains at different folders within public_html
Also a few rewrite commands in the .htaccess file in the public_html folder can redirect the domain pointing to that folder inso a sub folder as well so that all your domains are a different folder in the public_html folder.
All the files you don’t want directly accessible can be in another folder outside of public_html but included in the path that all your domains search for includes - in separate sub-folders corresponding to the different domains.
So if I have a domain point to /gallery/
/gallery/public_html/
/gallery/x/
The folder x can accessed from php script in public_html/ by going on folder back
…/x/…
Correct???
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.