Now that we understand the general requirements for hosting FE assets and backend functionality with Pages, let’s figure out how to get that working with Fulcro. Pages has a long list of supported frameworks, but, perhaps unsurprisingly, none of them are a CLJS framework. Luckily, remembering from the Pages overview post, we can either build the assets ourselves and commit them to our repo, or, possibly, we can specify a custom build command that will build the assets for us as part of the Pages infrastructure.

My core goal with this post is to break down how Pages, and Pages Functions, work together. Pages This link has a good overview of how to set up Pages for deployment. The two that interest me are the Git provider set up, and the wrangler cli. My default is to use the git provider configuration, as I’d like to deploy this on push to the main branch, but the wrangler cli may have some useful functionality to learn about.

To host this app, I’ll need the following things: Something to host the static assets, e.g. the html/css/js. Something to handle the state synchronization across clients To host a site that would allow for multi-user alteration of the content, static assets alone won’t be enough, as we’ll need a way to synchronize our changes across users. While automerge has many ways to exchange changes – essentially anything that can faithfully transmit or store binary data – if we want an always-on node that can act as a post-office of sorts, we’ll need to build the code that takes the binary data and puts it on that node.

I’ve got a project idea, which I’ve just now decided to call AutoFlare, that I’ve been rolling around in my head, primarily as a way to learn more about three technologies: Cloudflare’s cloud offerings Fulcro automerge CRDT I’ve got a lot of experience with AWS and GCP, and there are plenty of things I like about those platforms, but I’d like to branch out, and some of the blog posts I’ve seen from Cloudflare around network egress costs and things has got me curious.