Category — Blog Notes
My blog improvement project is still going, just very slowly. I have done more research on trac, Redmine, gitlab, and such, and after some thought I’ve decided to do the following:
- Migrate my trac site to Redmine.
- Create an account at gitlab and move my svn projects to gitlab.
- I will also update my WordPress installation, including fixing issues such as extra characters all over the place on old posts.
Some notes on these choices:
- I’m using Redmine to replace trac because it seems to have better import abilities, and is much easier to install on Webfaction (my hosting provider) than gitlab. Also, gitlab can use a lot of resources. Redmine also looks like a better match for my wiki style.
- I want to move from subversion to a distributed version control system. Although there are advantages to systems such as mercurial, git has by far the largest mind-share and support.
- I like the fact that gitlab supports both hosted (for here) and local (for work) servers, unlike alternatives such as github.
- Howerver, projects on github seem to be more visible and more easily found.
- Finally, if I run into some big road-blocks, I might change my mind.
November 28, 2016 No Comments
I’ve been using trac for about a decade, and overall it’s worked well. But I have found some annoyances over the years, such as:
- I have found it difficult to install, often requiring some searching for answers.
- I have found that upgrading to a new version can be an exciting adventure (but not an easy one).
- I have found migrating a trac installation to a new server to be difficult.
- I feel that trac development has been slow, and the trac interface has not kept up with recent advances in web interfaces.
Since my current trac installation isn’t perfect on 64-bit Linux, I will have to upgrade trac yet again or switch to something else.
If I switch to something else, it will be similar project management software with a wiki and such, because I will switch both here and at work. Another requirement is that I need to be able to easily migrate my trac wiki to a new system, which also rules out most wikis.
I have been investigating Redmine and Gitlab. Redmine is the most likely choice, but I need to do some more research and actually play a bit with both. Another similar, highly regarded, project is Phabricator, but it doesn’t appear to have good support for importing trac projects yet.
November 4, 2016 No Comments
Since I already have this main WordPress site, why do I have a trac site too? It’s because I’ve found that trac works better for some of the things I like to do.
Let’s take a look at where some of my content fits best:
- Typical blog posts, which describe what I am doing (like this one). These are a perfect fit for WordPress.
- A series of related blog posts. I could do this on trac (by continually updating the wiki), but WordPress feels like a better fit.
- Directories, such as my piezo motor page or my MCAD software page. I’ve tried both WordPress pages and trac wiki pages; over time, I’ve decided I prefer these topics on trac.
- Reference information on topics such as my motors and my cabling standards. These fit trac best, with its easy hyperlinking and table support.
- Repository viewing – only trac does this well, although I haven’t made much use of it (yet….)
- Bug tracking / project management – I haven’t used this yet, but this is where trac shines.
Why use trac instead of a dedicated wiki? Well, I originally picked trac for use at work, and since I knew it, it made sense to use it here. Also, I wasn’t expecting to use the wiki as much as I have.
November 3, 2016 No Comments