Separate private_html folder

R

rldev

Verified User
Joined
May 26, 2004
Messages
1,003
changing private_html to symlink at setup

Is there anyway to have DA set private_html up as a symlink to public_html by default when an account is setup?

Although I understand the concept of a seperate folder for ssl docs, it is just not practical for all intesive purposes. Most clients who use ssl use it for some type of shop or order form. It would be much easier to change the symlink to a physical directory since not many will request this.
 
I believe you can set up a post-user creation script to do it for you, but I've never tried.

Jeff
 
That would be interesting. Do you know who is the DA script guru on this board?
 
Sorry, I wasn't paying attention to my copy/paste. I'll have to see if I can find that thread again, I'll get back.
 
Symbolic Link to private_html

I would like a symbolic link to be created in the /home/username for private_html when you create a new user and when you set the default domain. At the moment only public_html symbolic link is created.

regards,
Onno
 
have noticed the same problem, I reckon this was more an oversight then a deliberate thing.
 
why seperate https folder?

Is there a particular reason why users have to place https documents in a different folder then regular http documents? I don’t really see the advantages as compared to the problems it causes.

For example:

1. How do frontpage extensions work since there is no option to install them to the https web docs dir?

2. Wouldn't most shopping cart programs have a problem with this setup?

3. I think 90% of users would have no use for a separate ssl docs dir or even know what to do with it.

I know I can remove the dir and create a symlink, but I would just rather have an account setup without this seperate https folder. I really don't see a compelling reason to have it. I mean if someone actually did want it, it could be setup and since the requests would be few and far between, it would not be a big deal.

Is it possible we can have an admin option to choose this in the admin cp for designated hosting plans?
 
Re: why seperate https folder?

rldev said:
Is there a particular reason why users have to place https documents in a different folder then regular http documents? I don’t really see the advantages as compared to the problems it causes.

For example:

1. How do frontpage extensions work since there is no option to install them to the https web docs dir?

2. Wouldn't most shopping cart programs have a problem with this setup?

3. I think 90% of users would have no use for a separate ssl docs dir or even know what to do with it.

I know I can remove the dir and create a symlink, but I would just rather have an account setup without this seperate https folder. I really don't see a compelling reason to have it. I mean if someone actually did want it, it could be setup and since the requests would be few and far between, it would not be a big deal.

Is it possible we can have an admin option to choose this in the admin cp for designated hosting plans?
Click to expand...

1. Frontpage don't work standard in HTTPS (Check forum, was a thread about it)

2. None will have problems with this as this is standard! All panels: CPanel, DA , Plesk etc. Why ? I don't think Apache would understand when it would or when it shouldn't use SSL. Please rethink things before posting! :D

3. It's their option to choose to use it ;) Disable SSL support for that user! :D
 
"Please rethink things before posting!"

LMAO :) Perhaps you may want to rethink things :)

"1. Frontpage don't work standard in HTTPS (Check forum, was a thread about it)"

This is not correct. DA's implementation may not work, but FrontPage does work over ssl.

"2. None will have problems with this as this is standard! All panels: CPanel, DA , Plesk etc. Why ? I don't think Apache would understand when it would or when it shouldn't use SSL. Please rethink things before posting!"

??? CPanel(don't think cpanel has a actual seperate dir, but symlink), DA , Plesk do not come anywhere near as to constituting the entire hosting world. My customers will have a problem because we use the same dir for http and https and nobody has ever requested otherwise.

Apache knows what to use based on what protocol a user selects. Apache doesn't care where you place documents so long as you tell it where document root is. How can any shopping cart system work when it goes to https for checkout?

3 options:
change ssl secure folder to a symlink to standard folder.
(simplest)
install entire cart to run over ssl
(makes little sense)
install two versions of the cart
(makes no sense)

So what is the compelling reason to have a seperate folder for https. I could understand one in a hundred wanting it, but not at the amount of headaches it causes.
 
I can do the following:

cd /usr/local/directadmin/data/templates
cp virtual_host_secure.conf custom
cd custom
pico virtual_host_secure.conf
Change the private_html to public_html and then just type:

code:echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

but this does not seem to work as the private_html dir is still created :) What script creates the actual directory structure intially and can this be converted to a custom script that will not be updated by DA?

will this make all future account setups adhere to this new rule set? I assume that DA is going to overwrite this file during an update. Is this correct? Anything I can do to make this permanent?
 
Last edited:
Well I just setup the domain_create_post.sh to remove the private_html dir so it was all rather easy to have it the way I want.
 
Symlink private to public folder

I have read the numerous topics regarding the symlink feature but none seem to give enough detail to allow the standard user to perform such a task.

I run an oscommerce website that uses http and https files. Currently I have to run two verions of the files...one in public and one in private to get the site to work properly and to allow SSL to work properly. This is very cumbersome and seems out of the ordinary.

I have enjoyed this host and support has been very good so I do not want to move my sites to another server.

What I need...and many others appear to have the same issue...is an easy to understand method to symlink the private folder to the public so that one set of files can be uploaded to the public folder and maintained instead of two.

I have many friends that use oscommerce that are interested in a good host but I cannot recommend them to switch over unless the task can be made simple to understand.

Any help is appreciated...and again thanks for a good reliable hosting solution.

Joe
 
You must have ssh access to follow these instructions. I do not think a link can be created through the DA Filemanager. It might be possible through ftp but I haven't tried it.

1. Login to your server via ssh
2. CD into your domains directory. (e.g. cd domains/yourdomain.com )
3. Remove you private_html directory rm -rf private_html (Careful)
4. Create the link using something like this
Code: 
ln -sf /home/username/domains/yourdomain.com/private_html /home/username/domains/yourdomain.com/public_html
 
1. I mean it doesn't work in DA :D

2. CPanel DOESN't Symlink! If you place a file in httpdocs it isn't in httpsdocs! At leas not in my setups.

I've seen a lot of panels through out the years and almost ALL have serparate dirs. The rest doesn't have SSL.

Why you would setup separate dirs ?? A lot of systems shouldn't be accessed in NON-SSL enviroments. Why ? Because of it's sensitive information.

If a non-technical client comes into you're site and by mistake comes under http:///xxxxxxx.xxx/checkout/ and the order could be processed without SSL and that way processed unsecure. (example credit-card information).

Most carts do have it in their code to check if the user is in SSL, but their are lots of carts that doesn't check it. (But why depend on the cart for this)

I think a lot of people could find more reasons why to have separate dirs instead of one dir, both SSL and Plain.

You can change this for your own server, but DA will not change this.

3. Exactly the correct way, just symlink it.
 
rldev is correct, it seems needless to have a seperate dir.

How does apache know when to be https? simple you send a https: request from your browser it is quite simple to have a page to function as ssl and non ssl.
 
symlink

OK...I have a reseller account but don't believe that SSH access is available to all users. Is this something the administrators can help with? Or is it possible to do thru the admin panel?

I generally use FTP to upload and download site files but I don't think I can access the required info to adjust this code. Coding looks simply enough but just want to be careful as I have live sites that could easily be disabled.

I understand that the intent of this host is to supply knowledgeable people who have half a clue with a good option and little support but I was unaware of the seperate folder for https files when I signed up. I am pretty good about figuring out most things but his one has me stumped.

So I am just looking for some good guidance from some members who have had the same problem.

Thanks for the previous post.

Joe
 
You must log in or register to reply here.
Back
Top