On Sat, Sep 6, 2014 at 9:52 AM, Miles Fidelman <mfidel...@meetinghouse.net> wrote:
> Scott Robison wrote: > >> ... One of my newest uses for fossil is the one case in which I'm using >> it distributed (even though all by myself): My blog (such as it is). It is >> not a unique idea at all, but I finally tired of heavy weight blog >> platforms and decided I wanted to just keep track of things in text files. >> I've started using the pelican static site generator to keep all my site's >> source files (restructured text files in a content tree & config files & >> etc) as well as the generated files (public tree). I only maintain the site >> on my home computer (including generating the public stuff), but then I >> commit & sync it to the remote server and update the live site, making the >> generated file tree available (and giving me a "live" backup of all the >> files). >> >> A little late getting back to this, but... > > Scott, can you say a little more about your tool chain, end to end from > editing to online? (I've been thinking about doing something similar, but > for maintaining some project documentation and works in progress). It's been a while since I started, so there may be some amounts of "hand waving" over things I don't remember exactly, but: 1. I installed the pelican static site generator along with its prerequisites: http://blog.getpelican.com/ 2. I had been using a private Wordpress installation, so I exported that database somehow and used some utility to convert it to restructured text files. 3. I use Notepad++ on Windows 7 for my text editing, and a command prompt for organizing files (moving or deleting some older blog posts that I didn't want in the exported blog for whatever reason). 4. I wrote a few simple scripts in PHP to provide a very basic chisel-esque management portal on my website; they are used to create repos, change passwords, and provide a front end to all my repositories. Using that I created my initial empty repo. 5. I cloned/opened the repo to my Windows 7 machine and added all the source and generated public files. 6. I synced that back to my server and opened the repo in the web directory, organized so that my public directory is the only one published. 7. Because I was porting an older blog to this new system, I had a fair number of media files (mostly images, some audio, a sprinkling of others) that were not in the Wordpress database, only in the old file system. So as I cleaned up each of the approximately 100 posts on my Win7 box, I would move media from the old location of my blog on the server to the open workspace, add them and commit them server side. 8. Update on Win7 to get the changes. 9. Regenerate the blog, addremove, commit, sync to the server. 10. Update the server side and check out my work, making any needed tweaks to ensure everything was presented essentially as I wanted it. 11. Repeat steps 7 through 10 for each of the posts. It's not a very impressive or sophisticated workflow IMO, but it did what I wanted quite nicely. While the blog itself is also not terribly impressive and not frequently updated (though I keep meaning to change that!) you can see it's current state at www.casaderobison.com. I've cleaned up all the posts and made sure all the media is available. I still have work to do cleaning up the category/tag system and tweaking the theme to my liking. I hope that answers the questions and wasn't *too* tedious. :) -- Scott Robison
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
