SHIFT-WIKI - Sjoerd Hooft's InFormation Technology
This WIKI is my personal documentation blog. Please enjoy it and feel free to reach out through blue sky if you have a question, remark, improvement or observation. See below for the latest additions, or use the search or tags to browse for content.
Argo CD - Fix exceeded max combined manifest file size
Summary: How to fix the error exceeded max combined manifest file size in argocd.
Date: 27 February 2025
A while ago I suddenly came across this error in Argo CD when trying to do a sync:
ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): failed to get potentially valid manifests: exceeded max combined manifest file size
This error is caused because the combined file size of all the manifests in the repository you want to sync with is too large.
Argo CD - Changing a Live Manifest
Summary: How to change a live manifest in argocd.
Date: 27 February 2025
In this post I'll show you how to change a manifest for a live application in Argo CD. This is useful when you need to make a quick change to a resource that is managed by Argo CD. In the last few months I've used this for changing all sorts of things, like image versions, resource limits and timeout settings for the liveness probe.
Apache Reverse Proxy
Summary: This is an overall page for an Apache reverse proxy, including installation, configuration, security and cache.
Date: Around 2011
Refactor: 20 February 2025: Checked links and formatting.
Apache Redirect
Summary: On this page I'll show you a redirect which can be used in a apache webserver.
Date: Around 2009
Refactor: 27 December 2024: Checked links and formatting. This is really old. If you're really looking for something like this contact me and I'll make you something. Please don't use this anymore.
This is a HTML redirect script. Replace '/gw/webacc' two times with where you want your web server to redirect and you're done. If your webserver listens to both http and https it will work for both protocols.
<html> <!-- This is all just a super-duper redirect to the Welcome page If the user has Javascript 1.1 installed, they don't get their history messed up. Otherwise, it behaves like a normal redirect, and even has fallbacks to non JS and browsers that don't handle the meta refresh tag --> <head> <script language="JavaScript"> <!-- var sThisURL = unescape('/gw/webacc'); function doRedirect() { actualRedirect(); } function actualRedirect() { setTimeout( "top.location.href = sThisURL", 500 ); } //--> </script> <script language="JavaScript1.1"> <!-- function actualRedirect() { // this is a better way to do it if we have JS 1.1, not adding // to the browser's history top.location.replace( sThisURL ); } if ( "MSIE" == navigator.appName ) doRedirect(); //--> </script> </head> <meta http-equiv="refresh" content="1;url=/gw/webacc" target="top"> <body bgcolor="white" marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" onLoad="doRedirect()"> </body> </html>
The redirect here is the redirect used for the login page for groupwise 7. For groupwise 6.5 it would be '/servlet/webacc'.