CloudLinux + cPanel Installation - Revision history

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:22:30Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:22, 1 September 2019
Line 65:		Line 65:
	Removing the two files fixed Softaculous.		Removing the two files fixed Softaculous.

	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]
	[[Category:Services]] [[Category:Guides]]		[[Category:Services]] [[Category:Guides]]

Leo: Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

2019-09-01T05:10:42Z

Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

← Older revision		Revision as of 05:10, 1 September 2019
Line 65:		Line 65:
	Removing the two files fixed Softaculous.		Removing the two files fixed Softaculous.

	[[Category:Linux]]~~{{Navbox Linux}}~~{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}
	[[Category:Services]] [[Category:Guides]]		[[Category:Services]] [[Category:Guides]]

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:09:38Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:09, 1 September 2019
Line 65:		Line 65:
	Removing the two files fixed Softaculous.		Removing the two files fixed Softaculous.

	[[Category:Linux]]{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}{{Navbox Linux}}
	[[Category:Services]] [[Category:Guides]]		[[Category:Services]] [[Category:Guides]]

Leo: Text replacement - "\[\[Category:Linux\]\][^{]+" to "Category:Linux{{Navbox Linux}} "

2019-09-01T05:00:35Z

Text replacement - "\[\[Category:Linux\]\][^{]+" to "Category:Linux{{Navbox Linux}} "

← Older revision		Revision as of 05:00, 1 September 2019
Line 65:		Line 65:
	Removing the two files fixed Softaculous.		Removing the two files fixed Softaculous.

	[[Category:Linux]] [[Category:Services]] [[Category:Guides]]		[[Category:Linux]]{{Navbox Linux}}
			[[Category:Services]] [[Category:Guides]]

Leo: /* Installing Softaculous */

2017-03-27T16:10:29Z

Installing Softaculous

@@ Line 46: / Line 46: @@
   chmod 755 install.sh
   ./install.sh
 [[Category:Linux]] [[Category:Services]] [[Category:Guides]]

Leo: Text replacement - "" to "}}"

2017-02-24T19:14:06Z

Text replacement - "</code>" to "}}"

← Older revision		Revision as of 19:14, 24 February 2017
Line 17:		Line 17:
	</syntaxhighlight >		</syntaxhighlight >

	Since cPanel runs out of {{code\|/usr/local/cpanel~~</code>~~, and because logs are placed in {{code\|/usr/local/apache/logs~~</code>~~, it's a good idea to give {{code\|/usr/local~~</code>~~ as much room as possible. The databases and configuration files for cPanel will be placed in {{code\|/var~~</code>~~. Your user's contents will be placed in their home directories in {{code\|/home~~</code>~~. For performance considerations, try putting {{code\|/var~~</code>~~ and {{code\|/home~~</code>~~ on a fast storage device.		Since cPanel runs out of {{code\|/usr/local/cpanel}}, and because logs are placed in {{code\|/usr/local/apache/logs}}, it's a good idea to give {{code\|/usr/local}} as much room as possible. The databases and configuration files for cPanel will be placed in {{code\|/var}}. Your user's contents will be placed in their home directories in {{code\|/home}}. For performance considerations, try putting {{code\|/var}} and {{code\|/home}} on a fast storage device.

	Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:		Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:

Leo: Text replacement - "`" to "{{code|"`


2017-02-24T19:12:30Z
Text replacement - "<code>" to "{{code|"

				
				
				
				
				
				← Older revision
				Revision as of 19:12, 24 February 2017
				
Line 17:
Line 17:
</syntaxhighlight > </syntaxhighlight >



Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code>, it's a good idea to give <code>/usr/local</code> as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device. Since cPanel runs out of {{code|/usr/local/cpanel</code>, and because logs are placed in {{code|/usr/local/apache/logs</code>, it's a good idea to give {{code|/usr/local</code> as much room as possible. The databases and configuration files for cPanel will be placed in {{code|/var</code>. Your user's contents will be placed in their home directories in {{code|/home</code>. For performance considerations, try putting {{code|/var</code> and {{code|/home</code> on a fast storage device.



Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run: Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:



Leo: /* CloudLinux */
2014-03-14T18:50:47Z
CloudLinux

				
				
				
				
				
				← Older revision
				Revision as of 18:50, 14 March 2014
				
Line 3:
Line 3:
== CloudLinux == == CloudLinux ==



Set it up using PXE or DVD. For my particular server, I have set my parition scheme up like so: Install CloudLinux using PXE or DVD.
 
For my particular server, I have set my partition scheme up like so:



<syntaxhighlight lang="text" line start="1" enclose="div"> <syntaxhighlight lang="text" line start="1" enclose="div">
Line 15:
Line 17:
</syntaxhighlight > </syntaxhighlight >



Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device. Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code>, it's a good idea to give <code>/usr/local</code> as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device.



Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run: Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:



Leo: /* CloudLinux */
2014-03-14T18:47:50Z
CloudLinux

				
				
				
				
				
				← Older revision
				Revision as of 18:47, 14 March 2014
				
Line 15:
Line 15:
</syntaxhighlight > </syntaxhighlight >



Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device.



Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run: Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:



Leo: /* CloudLinux */
2014-03-14T18:45:25Z
CloudLinux

				
				
				
				
				
				← Older revision
				Revision as of 18:45, 14 March 2014
				
Line 15:
Line 15:
</syntaxhighlight > </syntaxhighlight >



Since cPanel runs out of /usr/local/cpanel, and because logs are placed in /usr/local/apache/logs by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>.



Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run: Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:
  /usr/sbin/rhnreg_ks --activationkey=xxxxx-xxxxxxxxxxxxxxxxxxxxxxxxx   /usr/sbin/rhnreg_ks --activationkey=xxxxx-xxxxxxxxxxxxxxxxxxxxxxxxx



The activation key is found on your CLN account.   The activation key is found on your CLN account at https://cln.cloudlinux.com/rhn/activationkeys/List.do



Once activated, you will then be able to update the system. Once activated, you will be able to update the system.
  yum -y update   yum -y update

← Older revision		Revision as of 19:12, 24 February 2017
Line 17:		Line 17:
	</syntaxhighlight >		</syntaxhighlight >

	Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code>, it's a good idea to give <code>/usr/local</code> as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device.		Since cPanel runs out of {{code\|/usr/local/cpanel</code>, and because logs are placed in {{code\|/usr/local/apache/logs</code>, it's a good idea to give {{code\|/usr/local</code> as much room as possible. The databases and configuration files for cPanel will be placed in {{code\|/var</code>. Your user's contents will be placed in their home directories in {{code\|/home</code>. For performance considerations, try putting {{code\|/var</code> and {{code\|/home</code> on a fast storage device.

	Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:		Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:

← Older revision		Revision as of 18:50, 14 March 2014
Line 3:		Line 3:
	== CloudLinux ==		== CloudLinux ==

	~~Set it up~~ using PXE or DVD. For my particular server, I have set my ~~parition~~ scheme up like so:		Install CloudLinux using PXE or DVD.

			For my particular server, I have set my partition scheme up like so:

	<syntaxhighlight lang="text" line start="1" enclose="div">		<syntaxhighlight lang="text" line start="1" enclose="div">
Line 15:		Line 17:
	</syntaxhighlight >		</syntaxhighlight >

	Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> ~~by default~~, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device.		Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code>, it's a good idea to give <code>/usr/local</code> as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device.

	Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:		Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:

← Older revision		Revision as of 18:47, 14 March 2014
Line 15:		Line 15:
	</syntaxhighlight >		</syntaxhighlight >

	Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>.		Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>. For performance considerations, try putting <code>/var</code> and <code>/home</code> on a fast storage device.

	Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:		Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:

← Older revision		Revision as of 18:45, 14 March 2014
Line 15:		Line 15:
	</syntaxhighlight >		</syntaxhighlight >

	Since cPanel runs out of /usr/local/cpanel, and because logs are placed in /usr/local/apache/logs by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>.		Since cPanel runs out of <code>/usr/local/cpanel</code>, and because logs are placed in <code>/usr/local/apache/logs</code> by default, it's a good idea to give it as much room as possible. The databases and configuration files for cPanel will be placed in <code>/var</code>. Your user's contents will be placed in their home directories in <code>/home</code>.

	Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:		Once the install is done, you will need to activate the license with CloudLinux's CLN. To do so, run:
	/usr/sbin/rhnreg_ks --activationkey=xxxxx-xxxxxxxxxxxxxxxxxxxxxxxxx		/usr/sbin/rhnreg_ks --activationkey=xxxxx-xxxxxxxxxxxxxxxxxxxxxxxxx

	The activation key is found on your CLN account.		The activation key is found on your CLN account at https://cln.cloudlinux.com/rhn/activationkeys/List.do

	Once activated, you will ~~then~~ be able to update the system.		Once activated, you will be able to update the system.
	yum -y update		yum -y update

CloudLinux + cPanel Installation - Revision history

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

Leo: Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

Leo: Text replacement - "\[\[Category:Linux\]\][^{]+" to "Category:Linux{{Navbox Linux}} "

Leo: /* Installing Softaculous */

Leo: Text replacement - "" to "}}"

Leo: Text replacement - "" to "{{code|"

Leo: /* CloudLinux */

Leo: /* CloudLinux */

Leo: /* CloudLinux */

Leo: Text replacement - "`" to "{{code|"`