I use DFS-R on a bunch of Windows 2008 R2 Standard Webservers for the web content without a problem. They all need to be members of a domain, but I remember the wizard being fairly clickety-straightforward.
You simply install the DFS components on all the servers you want to sync, and then on one of them set up all the replicated folders and add all the clients to that replicated folder.
This link seems to cover the steps quite well.
N.B. - you say 'realtime' - this means different things to different people. What sort of a lag is tolerable for you? Solutions vary (in complexity and cost) depending on whether you can tolerate 5 minutes, 5 seconds, or 5 milliseconds.
I missed where you said you had Server 2008 R2 Web Edition, you're right that doesn't come with DFS. This leaves you with two other options:
Save all runtime configures to some persistent shared storage, either a network drive that all nodes can see, or to a database somehow.
Hack together Robocopy, rsync, or some other filesystem sync framework to handle the replication.
Personally, I've never found (2) to be particularly reliable. It might work at first, but silent failures can cause a lot of issues. If it's only small files, (1) might not be a bad idea. In an ideally architected world, web servers shouldn't be storing transient but shared data on their filesystems anyway, precisely because of this synchronization issue. However, I appreciate that re-building everything just to solve this might not be the most available option. In this case, I'd probably push for resource to upgrade to Server 2008 Standard Edition - DFS really does work very well, and MS presumably removed it from Web Edition to push more advanced deployments onto Standard.
Alternatively, you can take a look at the IIS Web Farm Framework. I've never played with it myself, but it looks like it might have some filesystem syncrhonization features in it. I can't guarantee that it'll do what you want though.