Ken Smith did something surprising, he got a Fargo Publisher server up and running on his own. I hadn't anticipated that anyone but the most adventurous programmer would try this, at this stage in the development process. But that's because I know too much about how unfinished it is. Ken didn't know, so he went ahead. And to my surprise, it kind of worked.
It's good, because it helps me get organized to finish this part of the Fargo 2 project. You should be able to switch over to a new back-end without any concern. And operating a server should be something a poet can do. If Ken can get over the Heroku side of it, I can make the Fargo side of it work almost perfectly (no software is ever perfect, of course).
So I've fixed one of the biggest remaining problems -- redirected from an outline name to the website rendering for that outline. You should be able to type kim.smallpict.com into a browser, and be taken to Kim's site. That used to work in the Trex days, and it works for smallpict.com only because I jury-rigged something temporary to make it work. And if you do it with Ken's domain I'm pretty sure it doesn't work.
However, in Fargo Publisher 0.79 that should be fixed.
Download the Fargo Publisher folder from GitHub as you did before, and replace your old copy of publisher.js with the new one.
At the command line, update the running version of the app with these commands.
git commit -a -m "Update"
git push heroku master
Assuming the domain you're managing is bumpy.org, you'd issue this command"
heroku domains:add *.bumpy.org
Of course *.bumpy.org should be mapped, via DNS, to be a CNAME for the domain of your Heroku app.
The way to test it is to do the following:
In Fargo, open an outline that's being managed by your Fargo Publisher server.
Put the cursor on a document.
Click the Eye icon.
Did it work?