Differences

This shows you the differences between two versions of the page.

--- binarylane-solutions:scoped-api-proxy:deployment [04/08/2026 00:00] – created - external edit 127.0.0.1
+++ binarylane-solutions:scoped-api-proxy:deployment [04/08/2026 02:35] (current) – external edit 127.0.0.1
@@ Line 14: / Line 14: @@
 ===== 1. Create the VPS =====
-Review and copy the [[https://raw.githubusercontent.com/01ax/binarylane-scoped-api-proxy/main/generated/bl-scoped-gateway-cloud-init.yaml|current raw cloud-init payload]] into the cloud-init or user-data field when creating the VPS.
+Paste the following into the cloud-init or user-data field when creating the VPS:
+<code yaml>
+#include
+https://raw.githubusercontent.com/01ax/binarylane-scoped-api-proxy/345182cc82741b702e9eaa792c34052bf9454b72/generated/bl-scoped-gateway-cloud-init.yaml
+</code>
+Cloud-init downloads the reviewed payload at first boot and processes it as though it had been pasted directly. The URL is pinned to a specific commit so repeated deployments use the same configuration. The VPS needs outbound HTTPS access to ''raw.githubusercontent.com'' during first boot.
+You can [[https://github.com/01ax/binarylane-scoped-api-proxy/blob/main/generated/bl-scoped-gateway-cloud-init.include.yaml|open the copyable include file]] or [[https://github.com/01ax/binarylane-scoped-api-proxy/blob/main/generated/bl-scoped-gateway-cloud-init.yaml|review the complete payload]] before deploying. The include is only read at first boot; it does not update an existing VPS if the repository changes.
 The payload installs the project under ''/opt/bl-proxy'' and pulls the container images. It does not start the public proxy listener or contain your API token.