m.muiznieks Comments - Answer Overflow

m.muiznieks

•Created by syrinj on 1/16/2025 in #zaraz

Using Zaraz with non-Cloudflare nameservers

You need at least one domain that is connected to the cloudflare. Then by following this example you can integrate that as many pages as needed. I currently have the Zaraz script installed on 7 different web pages, some of them are also on separate Cloudflare accounts.

3 replies

CDCloudflare Developers

•Created by syrinj on 1/16/2025 in #zaraz

Using Zaraz with non-Cloudflare nameservers

@syrinj https://developers.cloudflare.com/zaraz/advanced/domains-not-proxied/ This works.

3 replies

CDCloudflare Developers

•Created by m.muiznieks on 1/11/2025 in #zaraz

Workflow bindings

For now, I think there is no better way than firing the http post request to the specific workflow. Ok, I still hope for some updates. :/

6 replies

CDCloudflare Developers

•Created by Victor on 1/13/2025 in #zaraz

Found another zaraz dashboard bug - When

I've noticed that the event properties are switching off after each time there are made some changes. This happens to any trigger. 1. Create it, 2. Save it 3. When edits are made - it switches off and if left unnoticed - no events are sent.

6 replies

CDCloudflare Developers

•Created by m.muiznieks on 1/11/2025 in #zaraz

Workflow bindings

@yo'av Sorry for disturbing you, but I believe you are one of few who can make some comments about this topic (and I hope you will).

6 replies

CDCloudflare Developers

•Created by m.muiznieks on 1/11/2025 in #zaraz

Workflow bindings

So, I am reading here: https://developers.cloudflare.com/workflows/build/call-workflows-from-pages/#use-service-bindings That Workflows can be triggered and connected as the Service Bindings. I made a template Workflow without any modifications made (so the code is useless here). I'm trying to get it alive as this:

export interface Manager extends OriginalManager {
    ext: {
        env: {
            KV: KVNamespace;
            KV2: KVNamespace;
            SERVICE_WORKER_THAT_WORKS: {
                fetch: (url: string, init: RequestInit) => Promise<Response>;
            };
            WORKFLOW: Workflow; //Does not work
                        // WORKFLOW_TEST_2: Service; //Does not work
                        // WORKFLOW_TEST_3: {
            //     run: (options?: WorkflowInstanceCreateOptions<unknown> | undefined) => Promise<WorkflowInstance>; //this is named as the actual function in template
            // };
                        // WORKFLOW_TEST_4: {
                create: (options?: WorkflowInstanceCreateOptions<unknown> | undefined) => Promise<WorkflowInstance>; 
                        //...
            };
                        
        };
    };
}

export interface Manager extends OriginalManager {
    ext: {
        env: {
            KV: KVNamespace;
            KV2: KVNamespace;
            SERVICE_WORKER_THAT_WORKS: {
                fetch: (url: string, init: RequestInit) => Promise<Response>;
            };
            WORKFLOW: Workflow; //Does not work
                        // WORKFLOW_TEST_2: Service; //Does not work
                        // WORKFLOW_TEST_3: {
            //     run: (options?: WorkflowInstanceCreateOptions<unknown> | undefined) => Promise<WorkflowInstance>; //this is named as the actual function in template
            // };
                        // WORKFLOW_TEST_4: {
                create: (options?: WorkflowInstanceCreateOptions<unknown> | undefined) => Promise<WorkflowInstance>; 
                        //...
            };
                        
        };
    };
}

I tried various ways, up there are few of what I tried. The only thing that works is fetching. What I get is the error:

X [ERROR]   TypeError: The RPC receiver does not implement the method "create".

X [ERROR]   TypeError: The RPC receiver does not implement the method "create".

This error is for whatever I try (except fetching). Adding a note for this - for the SERVICE_WORKER_THAT_WORKS I have few more methods, that works at other cross-worker bindings, but with zaraz custom managed component I get the same error as above. the Bindings in wrangler.toml

binding = "WORKFLOW"
service = "wf-name-in-cf"
entrypoint = "MyWorkflow"

binding = "WORKFLOW"
service = "wf-name-in-cf"
entrypoint = "MyWorkflow"

I tried with and without entrypoint. Adding the [[workflows]] does not work also, as it throws warning, that it is not recognized and does not appear to bindings.

6 replies

CDCloudflare Developers

•Created by m.muiznieks on 1/11/2025 in #zaraz

Workflow bindings

Yes, I know about the Bindings in general, and I found out that through one of your GH repo examples. I'm using the MC in more than one page and working on custom GA4, FB event processing and want to "remove" that functionality from the MC itself, instead sending and processing the events separately (which includes saving some events on D1 as well). While exploring the Workflows I thought this might be a good use for them. I ask this because I see that MC publishing uses the old 3.29 Wrangler version, which does not recognize the Workflows in wrangler.toml Other way around is using http fetch of course, but..

6 replies

CDCloudflare Developers

•Created by Jonh Wick on 12/27/2024 in #workers-discussions

The struggle is real. I can only imagine

Yes. As far as I've experimented, I understand that it is possible to deploy much more than just described frameworks within the documentation. I also have managed to deploy a tanstack router as well, but everything stopped at the Env variables. I must admit, that was few months back, so now I understand there is some ways how to implement it, but I havent foloowed to that anymore (as its still in development process).

12 replies

CDCloudflare Developers

•Created by Jonh Wick on 12/27/2024 in #workers-discussions

The struggle is real. I can only imagine

Yes, I kind of don't understand that getting the frameworks on the "stage" is one thing, but the pain point (for me) is always getting the Environment variables and bindings to show up. Regarding the RR7, nothing that worked with Remix - didn't work on RR7. Figuring out the errors took one week as official RR7 Cloudflare template is not doing the job correctly (unless deciding not to use Env variables).

12 replies

Gaming

Programming