Setting up Expense Tracker

HOME > EXPENSE TRACKER SETUP GUIDE

Setting up Expense Tracker is a four step process.

1. Download source code from Github.
2. Make config changes as necessary.
3. Build Expense Tracker.
4. Run Expense Tracker

Step 1: Download source code from Github

If you do not have Git already on your machine, install it. In the Git command shell, type:

git clone https://github.com/arunkpatra/expense-tracker.git

Step 2: Make config changes as necessary.

You can provide your own database or use a embedded database for demonstration purposes. Please note that, in demo mode, data is not persisted between restarts. For production mode, you must supply your own database. See Database Setup. You will also have to setup an email provider. See Email Configuration.

Step 3: Build Expense Tracker.

If you do not have maven on your machine, install it. Issue the following command to build the expense-tracker.war file. The war file will be saved in your local maven repository.

mvn clean install

Step 4: Run Expense Tracker

You would deploy the expense-tracker.war file to a servlet container like Tomcat or a full blown app server like Websphere Application Server or Weblogic. If you choose to use the embedded database and run your app in demo mode, you just deploy it to your runtime. No other config changes are required. However, if you choose to supply your own database and run it in production mode, you must supply -Dspring.profiles.active=production as a JVM startup property. Note that, if you are using an App Server like Websphere Application Server or Weblogic, be sure to invert the classloader - i.e. use PARENT_LAST classloading policy.