iJobz – Job Management Portal

iJobz a Job Management Portal helps the job seekers to post the resume and apply for a particular job and the job recruiters can post the job openings in their company. Using the Job seekers module the seekers can update their profile and add their resume to the system. The updated resume can be viewed by the recruiters. each seeker has their own user account and they can view the Applied Jobs and Saved Job. The job seekers can view the list of jobs posted in the website.

In the Job Recruiters, the employers can post their jobs, view the resumes of the job seekers and can control their job. The admin can add, edit or delete data whenever needed without any assistance. The details that need not be displayed in the website can be de-activated by the admin instead of deleting it. So the details will remain as such for later reference by the admin but will be restricted for the user only.

Job Management Portal Features

  • Login Management
  • User Account
  • Job Seekers
  • Profile Update
  • Resume Upload
  • More than one resume upload
  • Apply Job
  • View Applied Job
  • Saved Job
  • Job Recruiters
  • Post Job
  • Job Status
  • Search Resume
  • Advertisement
  • Contact Us

41a

 Additional Features

  •  Customized Design – The design of the website will be customized to your need by our team of creative designers who validate with latest web standard and best User experience design.
  • Responsive design – The website will be Responsive i.e can be viewed in varied devices with different resolution. The website will be compatible in all major browsers.
  • W3C compliant XHTML & css coding
  • Website speed optimization
  • Compatibility in all major web browsers
  • Easy Navigation
  • SEO friendly design
  • Use Your Own Custom Domain
  •  Monitor Your Traffic with Analytics
  •  Rock Solid Cloud Hosting
  •  Unlimited Bandwidth

Advantages

  •  OnDemand / Self-Hosted
  •  Best Business Solution
  •  Quick turnaround time
  •  Theme Integration
To know more about our web and mobile development service visit http://evincetech.com.
For more information, please contact us with the specifications for your project. You can email our sales team at info@evincetech.com, also you can call us at following numbers.
India: (+91) 44 42170775, (+91) 91766 40375
USA [Toll Free]: 866 220 6565

Setting Up Subversion Server on Ubuntu

Step 1: Installing the Subversion package

#apt-get install subversion

Step 2:  Configure Subversion Directory

#mkdir –p  /home/svn/repository

Step 3: Configure Subversion group

#groupadd svn

#chgrp svn /home/svn/repository

#chmod g+rw /home/svn/repository

(you need to make sure that all new files and directories created in the repos directory (in other words, anything committed to the repositories) will also be owned by the group)

#chmod g+s /home/svn/repository

#usermod –a –G svn user1 (Assign users to svn group)

#usermod –a –G svn user2 (Assign users to svn group)

Step 4: Creating a New repository

#svnadmin create /home/svn/repository/test

Step 5: Checkout Repository

#svn checkout file:///home/svn/repository/test

Output: Checked out revision 0

Step 6: Add new files to Empty repository

#cd test

# echo ‘Hello, World!’ > hello.txt

#svn add hello.txt

Output : A         hello.txt

Step 7 : Commit files

#svn commit -m “Added a ‘hello world’ text file.”

Output :

Adding         hello.txt

Transmitting file data .

Committed revision 1.  Website Maintenance Services 

To know more about our web and mobile development service visit http://evincetech.com.
For more information, please contact us with the specifications for your project. You can email our sales team at info@evincetech.com, also you can call us at following numbers.
India: (+91) 44 42170775, (+91) 91766 40375
USA [Toll Free]: 866 220 6565

Use of svn in web application

Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your data or examine the history of how your data changed. In this regard, many people think of a version control system as a sort of “time machine.”

Managing web applications in SVN is tricky for some reasons:

When using revision control, a programmer is always working on a ‘working copy’ of the project. In traditional software engineering, this copy is somewhere on the his machine, as it’s a stand-alone application. In web development, however, we’re talking about webspace. Should every developer have a PHP environment on his machine then? Shouldn’t all programmers work on the exact same server configuration? What about Windows and Mac users? Web Application Development India

This means the working copies should be best on one webserver, along with an SVN client. Thus, we need some interface (the most simple one being SSH) to access it. Maybe a rich web client would be even better.

The application needs to be deployed to a live webspace. This might happen quite often and should be as painless as possible.

Version Control Terminologies

Let us start by discussing some of the terms that we will be using in this tutorial.

Repository: A repository is the heart of any version control system. It is the central place where developers store all their work. Repository not only stores files but also the history. Repository is accessed over a network, acting as a server and version control tool acting as a client. Clients can connect to the repository, and then they can store/retrieve their changes to/from repository. By storing changes, a client makes these changes available to other people and by retrieving changes, a client takes other people’s changes as a working copy.

Trunk: The trunk is a directory where all the main development happens and is usually checked out by developers to work on the project.

Tags : The tags directory is used to store named snapshots of the project. Tag operation allows to give descriptive and memorable names to specific version in the repository.

Branches: Branch operation is used to create another line of development. It is useful when you want your development process to fork off into two different directions. For example, when you release version 5.0, you might want to create a branch so that development of 6.0 features can be kept separate from 5.0 bug-fixes.

Working copy: Working copy is a snapshot of the repository. The repository is shared by all the teams, but people do not modify it directly. Instead each developer checks out the working copy. The working copy is a private workplace where developers can do their work remaining isolated from the rest of the team.

Commit changes: Commit is a process of storing changes from private workplace to central server. After commit, changes are made available to all the team. Other developers can retrieve these changes by updating their working copy. Commit is an atomic operation. Either the whole commit succeeds or is rolled back. Users never see half finished commit.

To know more about our web and mobile development service visit http://evincetech.com.
For more information, please contact us with the specifications for your project. You can email our sales team at info@evincetech.com, also you can call us at following numbers.
India: (+91) 44 42170775, (+91) 91766 40375
USA [Toll Free]: 866 220 6565