Add Cloudflare worker automation scripts

.github/workflows/worker.yml

@@ -0,0 +1,29 @@
+name: Deploy Worker to Cloudflare
+
+on:
+  push:
+    branches: ["master"]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: worker
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Install Wrangler
+        run: npm install -g wrangler
+
+      - name: Configure Wrangler with API Token
+        run: |
+          wrangler config --api-key
+        env:
+          CF_API_KEY: ${{ secrets.CF_API_TOKEN }}
+
+      - name: Publish the Worker
+        run: wrangler publish --env production
+        env:
+          CF_ACCOUNT_ID: ${{ secrets.CF_ACCOUNT_ID }}
+          CF_API_TOKEN: ${{ secrets.CF_API_TOKEN }}

worker/worker.js

@@ -0,0 +1,27 @@
+addEventListener('fetch', event => {
+    event.respondWith(handleRequest(event.request));
+});
+
+async function handleRequest(request) {
+    // Modify the request URL
+    const url = new URL(request.url);
+    url.protocol = 'http:';
+    url.hostname = 'host.btiplatform.com';
+    url.port = '8080';
+
+    // Fetch the data from the modified URL
+    const response = await fetch(url.toString(), request);
+
+    // Create a new response with CORS headers
+    const newHeaders = new Headers(response.headers);
+    newHeaders.set("Access-Control-Allow-Origin", "*"); // Adjust as needed for security
+    newHeaders.set("Access-Control-Allow-Methods", "GET, POST");
+    newHeaders.set("Access-Control-Allow-Headers", "Content-Type, Authorization");
+
+    // Return the response with the new headers
+    return new Response(response.body, {
+        status: response.status,
+        statusText: response.statusText,
+        headers: newHeaders
+    });
+}

wrangle.toml

@@ -0,0 +1,8 @@
+name = "api"
+
+[site]
+bucket = "./worker"  # Path to your worker code
+
+[env.production]
+# The account_id is set through an environment variable in the GitHub Actions workflow
+account_id = "$CF_ACCOUNT_ID"