One of the requirements I had, was to be able to run multiple instances of gollum, as well as using systemd to start and stop these instances easily. There is a gollum package in the AUR, but this does use the webRick, and therefor I decided to start from scratch.
In this post I would like to gather some personal requirements for a NAS System I am going to build.
Right now, I am in the process of ripping all my CDs (around 950 unique releases – More than half of it is already finished). The target is to store all these releases on a personal NAS with the ability to stream those to my stereo. For this I have already selected minimserver as the UPNP-Server. This server has the requirement of a JDK to let it run. Therefore the NAS I am going to build must have the ability to run JAVA.
Since Linux offers a “similar” File System (btrfs) I would like to use this one for the NAS.
The services which I would like to run on the NAS are then the following:
- Web Server
- Arch Linux – The distro I know the best
- Possibility to run Virtualbox
There some other options, which would be nice, but are not as “necessary”. There is e.g. Ajenti, which provides a nice WebGUI for the administration of the NAS, but this does not really correspond to the way Arch Linux works 😉 A possibility would be to use e.g. CentOS or
Ubuntu as a distro, but I am unsure, if this is really going to work out, just for a nice GUI????
The above mentioned requirements are not really tough for todays hardware and therefor I would like to stick to the Stack provided in the nas-portal forum (see here).
Since I am going to use a filesystem, which seems to be picky about power outages, I am in need of a UPS, and I am currently thinking about this one.
So I am going to explain some more interesting stuff about the tagging of my FLACs for the minimserver and about the used tool (discogstagger) in some future posts. Stay seated, so that you can see how an absolute Hardware Noob tries to build his own NAS 😉
Today I wanted to install SparkleShare-Dashboard on my Linux Laptop. I was pretty glad, since it is a nodejs application and the target plattform, where I would like to install this application finally, will be a nodejs system (ArchLinux ARM) as well.
There is also a little „difficulty“ and probably a miss-understanding in the community of how to create a „SparkleShare-Git-Repository“. I have done it, therefore please find a step-by-step guide:
mkdir -p /home/USERNAME/sparkle/public.git
git init --bare
git clone file:///home/USERNAME/sparkle/public.git
git add README.txt
git commit -m "Initial commit"
git push origin master
rm /tmp/public -rf
This should be it, you do have an initial commit in the repository, and therefor SparkleShare can attach the id to the repository (the id is the SHA1-id of the first commit in the repository).
Since I am using Arch Linux, I am more then accustomed to using the latest and greates versions of all the stuff. Unfortunately this is not always very good. During the last couple of days I experienced a couple of class loading issues with Java 7 (as opposed to Java 6).
I am currently testing Broadleaf Commerce and had to report an issue to theses guys because of some problems I did receive during compilation and running this application. Something similar happened to me on my project at work as well. I call this „class loading issues“, but it is probably slightly more. I do have problems loading configuration data correctly. (see issue 96 on the Broadleaf JIRA)-
To work around this issue, I just installed Java 6 again. Now it is working like a charm.
on Monday this week (the 21 Feb. 2011) we released the latest ArchServer Release Candidate 3. Hope that this one will be donwloaded as much as RC2 and we are receiving some more interest in the project. You can find a detailed list of all the news and fixes in this release on the News page on the ArchServer Homepage.
Today I need to connect to the serial console of a VBox instance to test the serial console boot and connection of the guest system (ArchServer that is). There seem to be a lot of ways on how to do this, I am just explaining, what works for me, using Arch Linux as the Host:
socat UNIX-CONNECT:/home/triplem/com1 TCP-LISTEN:8040 telnet localhost 8040
This was not working, in that I always received strange Characters in my terminal as soon as I used e.g. the cursor keys. This did not work, even after changing the terminal emulation to VT100 and all others.
The same is true for socat unix-client:/home/triplem/com1 stdout
I do not seem to be able to work with this kind of stuff, the following tip was not working as well:
Work with VBox and serial console.
I am using the public ZNC (an IRC bouncer) from globalshellz.org for my access to the freenode IRC network. I have had a minor problem when I connected to my ZNC. Since my away nick was not registered to my account (which is triplem btw), I have had to „login“ each time when I connected to the ZNC and my nick was changed from triplem[a] to triplem. So, I started my IRC client (XChat btw) and forgot to type in my password again, this lead to a problem that my nick was temporarily unavailable. To resolve this I looked on the freenode page and found the following easy solution:
- Registered my away nick with /nick triplem[a] and /msg nickserv group (of course I needed to login to my account, which was not a problem, since several nicks are already grouped to my main nick and I just chose one of those).
- I released the original nick (triplem) with the following command: /msg nickserv release triplem
, and everything was fine.
Hope this helps you as well. And if you would like to meet me on IRC, you can take a look into the following channels:
Probably we meet us there 😉
I am just thinking, that just providing some Toolset, like the ALM Stack is not enough. There is some documentation needed, not only for configuration, maintance and usage of the ALM Stack, but also some hints and best practices for the handling of projects.
Since we are already providing a wiki in our toolbox (Redmine contains a wiki), we will most probably provide an initial project in Redmine which will be configured the „right“ way and contain some documentation.
Most of these best practices are already documented elsewhere, so we will mostly provide links to these resources, as well as additional resources we can provide ourselves.
If you have any input on this, do not hesitate to contact me anytime.
Please take a closer look onto the newest addition of the ArchServer distribution. I have just published a ALM (Application Lifecycle Management) Stack for this distro with all ALM related tools already installed.
The stack contains the following components:
- Redmine – project management software (bug tracking, wiki, forums, …) found at http://redmine.org
- Hudson – Continuous Integration Tool found at http://hudson-ci.org
- Maven – the java build management Tool found at http://maven.apache.org
- Sonar – Quality Management Software found at http://sonarsource.org
- Nexus – Maven Repository Management found at http://sonatype.org
- Git – Distributed Version Control found at http://git-scm.org
You can find all scripts to install such a stack (I named the stack Archlinux Development Stack earlier on, but it should now be called ArchServer ALM Stack), on Github. There is also additional information about this stack. In the near future I hope to add more components as well as more documentation. The documentation should then be also put into the ArchServer.org wiki.
The Virtualbox image itself can be found on our mirror at http://mirror.archserver.org/iso/vbox/ArchServer-ALMStack-20110101-i686.vdi.lzma. The image is lzma-compressed, so you need lzma to decompress the image.
Finally, we have made it and published our first Release Candidate. This one is just for testing purposes. Read the full news here. Please download an ISO and help us testing this newest Release. Any Feedback is welcome 😉