Showing posts from 2015

Building my Homeserver : Webmin administration

It’s time to install webmin .  Webmin is a web based system administration for unix based system. Webmin is accessible through any browser. For more info visit the website . But before we need to setup something  before. It’s a minimal install so it needs to install wget first. yum install wget Next we will install some other requirements for webmin yum -y install perl perl-Net-SSLeay openssl perl-IO-Tty There’s actually 2 ways to install webmin as the website states . One is using the yum repos and other is downloading the rpm. I prefer rpm that’s why i installed wget first. Next we will download the webmin rpm. wget Next we will install the rpm rpm -U webmin-1.760-1.noarch.rpm Once the webmin is installed it is accessible through the network using the port 10000 and also through https. But in centos we need to add the port and https in to the firewall. Run the following commands.

Building my Homeserver : Operating System

It’s the second part of my homeserver build. You can find the first part here . I have initially planned to use NAS4Free for the os. But later changed to Centos 7 as Redhat distributions were my favourite one. And also i would like use GitLab and need run the server as well as NAS server as well as a testing Home Server. As it’s hard to use a  wired  connection to the router i compelled to use a Wifi dongle which will not be supported by the NAS4Free. First installed Centos 7 ( 1406 ) minimal install. To my surprise it detected the WIfi dongle i have used the static ip of Using RAID 10 in my 4 500GB HDD i have successfully installed the server and also i have installed the Webmin which will accesible through . But when i updated the packages the Wifi simply stop to work. It’s showing in the nmtui but not activating . It’s status is DOWN. Then i downloaded Centos 7 ( 1503 ) and reinstalled it. The problem is it’s showing in the installa

Building my Homeserver : Hardware

I have been planning to build a cheap home server since my external HDD failed unexpectedly. My initial search leads to FreeNAS. But after posting foolish questions in forum i found out that it requires better hardware as it’s based on ZFS. ECC supported RAM and MOBO will be a cost overhead for my rig as i decided to go for some second hand hardware. Then i found this NAS4Free. It’s not simple as FreeNAS but it’s based on UFS so it need not be a heavy hardware. I bought a second hand i3 pc with four hdd and ran NAS4free for 3-4 days. One of it’s hdd failed sometime. I think the problem is with the PSU. So i bought a new Corsair vs450 .So that’s my rig. Lets see the spec. Mobo : Intel Desktop Board DH55TC CPU : Core i3 530 @ 2.93Ghz RAM : 2GB Kingston PSU : Corsair vs450 HDD : 1 x 500GB WD Green 3 X 500GB Seagate Here is some pictures :  Front : My 140MM deepcool Fan  Side View  HDD bay Mobo Ram My Cable Mangement (Later

MEAN js adding a CRUD module

it's continuation of previous post . Lets try to add  a new CRUD module to the app. First create a new module using the yo generator. We will create a new module to add a company name and it's location. yo meanjs:crud-module company It will ask some questions. Need to specify angular folders. Select all those. Next it will ask about menu. whether it need to be added or not. type 'Y' so it will create those links. So the module is loaded. If you check the app folder you will find some new files in the app. Currently it had option to add the name only. We will add location also. Lets edit that. Navigate to  model app/models/ and open company.server.model.js . This file consist the model of the module 'company'. This will define the mongoose schema . Lets add properties for this schema. var mongoose = require('mongoose'), Schema = mongoose.Schema; var CompanySchema = new Schema({ name: { type: String, default: '', req

MEAN js Application structure

It's a continuation of previous post . Lets discuss about the application structure in a MEAN.js Application. Actually MEAN follows a MVC(Model-View-Controller). There are mainly two types of application structure for MVC. 1. Horizontal Folder Structure         This type of structure follows the division on functional role rather than the feature.The files and folders will kept inside a application folder .  There will be one controller folder for all application controllers. Horizontal structure is for simple projects where the features were limited. An example for this structure is app ----controllers ----models ----routes ----views config ----env ----strategies ----config.js ----express.js public ----config ----controllers ----directives ----css ----filters ----images ----views ----services server.js package.json app folder consists of all the files or the server side files. app/controllers folder holds all express controller logic. app/models folder ho