Hello CFML
Create a CFML page at /opt/coldfusion2025/cfusion/wwwroot/hello.cfm that outputs "Hello, ColdFusion!" and the current server date. The page must return HTTP 200 and contain the string "Hello, ColdFusion!".
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
DevOps & K8S Consultant, Technical Content Writer AWS Community Builder, IBM Champion
Create a CFML page at /opt/coldfusion2025/cfusion/wwwroot/hello.cfm that outputs "Hello, ColdFusion!" and the current server date. The page must return HTTP 200 and contain the string "Hello, ColdFusion!".
Build the logging pillar on a Rancher cluster: install Grafana Loki to store logs and Grafana Alloy to ship them from every node, then wire Loki into the Grafana you already run for metrics and prove a LogQL query returns your cluster's logs. This is the same pipeline Rancher's Logging app packages.
Kong is already installed and routing a workload. Turn it from a plain ingress controller into an API gateway: attach a rate-limiting plugin to the route so the gateway rejects requests over the limit with HTTP 429.
Add the Kong Helm repository to Rancher's Apps, install the Kong ingress controller, and route a workload through the Kong gateway. This is the everyday platform-app workflow: add a repo, install a tool, and wire your workloads into it.
Add the Kong Helm repository to Rancher's Apps, install the Kong ingress controller, and route a workload through the Kong gateway. This is the everyday platform-app workflow: add a repo, install a tool, and wire your workloads into it.
Protect a Rancher installation against disaster. The Rancher Backup operator and a ResourceSet are already in place - create a Backup and confirm the operator produces a completed archive of the management state, the first step of any real recovery plan.
Run the continuous delivery loop against a self-hosted Gitea Git server: point Fleet at a repository, then commit and push a manifest change and watch Fleet reconcile it onto the cluster. This is the GitOps contract Rancher Fleet enforces - the cluster follows Git, with no manual kubectl apply.
Carve out a namespace for a team, cap its resource consumption with a ResourceQuota, and grant a user scoped read-only access with a Role and RoleBinding. These are the native Kubernetes primitives Rancher Projects and roles build on.
Prove you can navigate Rancher's Cluster Explorer by creating a namespace called rancher-explorer in the local cluster - using the UI, not the command line. A quick, hands-on check that you found your way around the dashboard.