BIG-IP - Revision history

Andre at 07:11, 14 June 2026

2026-06-14T07:11:18Z

← Older revision		Revision as of 09:11, 14 June 2026
Line 6:		Line 6:
	Upgrade the system, and then restore your "dehydrated"		Upgrade the system, and then restore your "dehydrated"

	'''commands, after restore:'''		=== '''commands, after restore:''' ===

	/etc/dehydrated/		/etc/dehydrated/

Line 14:		Line 13:
	chmod +x dehydrated		chmod +x dehydrated

	'''Crontab change:'''		=== '''Crontab change:''' ===

	crontab -e		crontab -e

Line 24:		Line 22:
	(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)		(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)

	'''Save your config:'''		== '''Save your config:''' ==

	tmsh save /sys config		tmsh save /sys config

	'''Making your cert:'''		== '''Making your cert:''' ==

	openssl pkcs12 -in your.pfx -clcerts -nokeys -out server.crt		openssl pkcs12 -in your.pfx -clcerts -nokeys -out server.crt

	openssl pkcs12 -in your.pfx -nocerts -nodes -out server.key		openssl pkcs12 -in your.pfx -nocerts -nodes -out server.key

Andre at 07:10, 14 June 2026

2026-06-14T07:10:15Z

← Older revision		Revision as of 09:10, 14 June 2026
Line 1:		Line 1:
	__TOC__		__TOC__

			== '''Upgrade:''' ==
	'''Upgrade:'''

	Make a backup first "/etc/dehydrated/ " this will be lost after a upgrade.		Make a backup first "/etc/dehydrated/ " this will be lost after a upgrade.

Andre at 07:09, 14 June 2026

2026-06-14T07:09:52Z

← Older revision		Revision as of 09:09, 14 June 2026
Line 1:		Line 1:
			__TOC__


	'''Upgrade:'''		'''Upgrade:'''

Andre at 07:07, 14 June 2026

2026-06-14T07:07:45Z

← Older revision		Revision as of 09:07, 14 June 2026
Line 15:		Line 15:
	'''Crontab change:'''		'''Crontab change:'''

	crontab –e		crontab -e

	'''Add the following line:'''		'''Add the following line:'''

Andre at 06:25, 14 June 2026

2026-06-14T06:25:14Z

← Older revision		Revision as of 08:25, 14 June 2026
Line 22:		Line 22:

	(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)		(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)


	'''Save your config:'''		'''Save your config:'''

Andre at 06:24, 14 June 2026

2026-06-14T06:24:55Z

← Older revision		Revision as of 08:24, 14 June 2026
Line 27:		Line 27:

	tmsh save /sys config		tmsh save /sys config

			'''Making your cert:'''

			openssl pkcs12 -in your.pfx -clcerts -nokeys -out server.crt

			openssl pkcs12 -in your.pfx -nocerts -nodes -out server.key

Andre at 06:16, 14 June 2026

2026-06-14T06:16:46Z

← Older revision		Revision as of 08:16, 14 June 2026
Line 22:		Line 22:

	(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)		(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)


			'''Save your config:'''

			tmsh save /sys config

Andre at 06:15, 14 June 2026

2026-06-14T06:15:45Z

← Older revision		Revision as of 08:15, 14 June 2026
Line 1:		Line 1:
	Upgrade:		'''Upgrade:'''

	Make a		Make a backup first "/etc/dehydrated/ " this will be lost after a upgrade.

			Upgrade the system, and then restore your "dehydrated"

			'''commands, after restore:'''

			/etc/dehydrated/

			chmod +x *.sh

			chmod +x dehydrated

			'''Crontab change:'''

			crontab –e

			'''Add the following line:'''

			15 10 * * 1 /etc/dehydrated/dehydrated -c 1>/var/log/dehydrated.log 2>&1

			(Will run every monday at 10.15u. Logs in /var/log/dehydrated.log)

Andre at 06:11, 14 June 2026

2026-06-14T06:11:41Z

← Older revision	Revision as of 08:11, 14 June 2026
Line 1:	Line 1:
		Upgrade:

		Make a

Andre: Blanked the page

2024-12-05T14:45:39Z

Blanked the page

← Older revision		Revision as of 16:45, 5 December 2024
Line 1:		Line 1:
	~~{\| class="wikitable"~~
	\|
	~~{\| class="wikitable"~~
	~~\|Why are so many companies so hostile against self-hosted versions of their product?~~
	\|}
	\|-
	\|
	~~{\| class="wikitable"~~
	\|
	~~\|<center></center>~~
	~~\|<nowiki>LinuxBender on Jan 21, 2023 \| parent \| next [–]</nowiki>~~

	I know the answer but I don't like my own answer. When a company hosts it's own code, they are in control of how it and the infrastructure their code is running on are managed. They can keep everyone on the same version and ensure all the servers are managed following a specific process. If there is a critical bug they can patch it right away, sometimes without getting into details.

	When people host a companies code, the vendor ends up with a lot more support cases due to externalities that the vendor does not control and the customers of the product will tweak and modify it in ways the vendor did not expect and does not support. The customer can see under the hood and find embarrassing mistakes. The customer may have network configurations and use cases that the vendor never expected their application to reside and function in.

	There are pros and cons to each method and both the vendor and customer stand to benefit from one method over the other but ultimately the vendor has to decide if they are willing to take on the extra support load and extra time to work with the customer to ensure best practices are followed for the app, the servers, for backups, for disaster recovery procedures, etc... In most cases the vendor does not have the ability to debug a customer hosted instance directly and depend on working with intermediaries sometimes over video chat screen sharing sessions.
	\|}
	\|}