cpanel3-skel files not copying

[danmc]

I have set up some files in /root/cpanel3-skel/public_html. when I make a new account, nothing get put into the newly created addon except the cgi-bin dir. I feel like I'm missing something, probably something silly. I have tried with files owned by root and owned by account. I have also tried putting them in /home/username/cpanel3-skel/public_html, still nothing. Is there a limit on complexity of the skeleton? Any help is appreciated!

Dan

 

[Infopro]

If you placed files here:
/home/username/cpanel3-skel/public_html

And that username is a reseller, and you were logged into WHM as that exact reseller when you created the new account, those files should have been copied properly.

Same as for root. You must be logged in as root when creating the account and want skel files pulled in from root skel directory.

 

[danmc]

If I look under "show reseller accounts" in WHM the reeller column haas one entry, root. The second column, the user column, has the user I have been using, so it doesn't look like that user is a reseller and the source of my problem. Is that it?

 

[cPanelTristan]

Any files in /root/cpanel3-skel/public_html should be placed into any new account owned and created by root. When you say the "newly created addon" are you talking about an addon domain? Addon domains will not have files put into them, only newly created accounts.

Can you please detail how you are creating the account or is this an addon domain rather than a newly created account that is being discussed?

 

[danmc]

You just sorted it out for me. It IS an addon, and so no files. Is there any way to accomplish the same thing?

 

[cPanelTristan]

You might create an addon domain hook that would copy files on addon domain creation:

http://forums.cpanel.net/f5/modify-addon-domain-creation-script-122805.html#post535629

 

[danmc]

Thanks for the help. I should have posted a long time ago! I've noticed most of those scripts are written in perl. Can I write one in PHP, using CLI? thanks, again.

 

[danmc]

Never mind, I got off my butt and looked at the docs. Still, I believe I heard a collective sigh from forum moderators everywhere thanks again for the help.

 

[Infopro]

You just sorted it out for me. It IS an addon, and so no files. Is there any way to accomplish the same thing?

There is an open Feature Request going on here:
http://forums.cpanel.net/f145/case-48382-skeleton-directory-addon-sub-domains-146569.html

 

[danmc]

The addon hook works great. In a way, it's even better, since I can do more than just have the files copied. In this case, I can set up the configuration files in the file set that's being copied with the custom settings specific to the domain being processed, as well as some other things. Thanks for the help and advice.

Dan

 

[OcalaDesigns]

Does anyone know how much you can put in this /root/cpanel3-skel/public_html directory? Like, could I add the whole Wordpress base installation since every account I add will use WordPress, then all I would have to is add the database, the database info to the config file and go ... or is that to much data to have in there?

 

[Infopro]

Sure you can do that. I would think you wouldn't want the installer to operate though and thats what would come up when the site is accessed right out of the gate of course.

 

[OcalaDesigns]

Yeah, that's what I want as the sites I host are completely controlled by me on my vps for security, they are all wordpress sites, and if a user/site is created, i am there to finish the install immediately. I have tested it and it works great. I make a user for each account so there are no shared hosting spaces or addon domains for security purposes. If one site actually gets compromised, they should not be able to traverse to the other sites making cleanup a lot simpler. wp-config is not in a public directory and an un-signed ssl for administration for each site. The website owners do not have access to the cpanels, only to wordpress.

 

[Infopro]

Nice, good luck!