This project is a simple expense tracking app. User has to create username and password to being able to use the app. After successfull login user can create expenses for each month based on categories, user can increase expenses and see total amount spent every month.

• Ruby 2.7.4
• NodeJS (v16), and npm
• Heroku CLI
• Postgresql

See Environment Setup below for instructions on installing these tools if you don't already have them.

Start by cloning this repository to your local environment

$ git clone https://github.com/Ewelajna14/phase4-rails-ruby-project your-project-name
$ cd your-project-name

To run project, run:

bundle install
rails db:create
rails db:migrate db:seed
npm install --prefix client

You can use the following commands to run the application:

• rails s: run the backend on http://localhost:3000
• npm start --prefix client: run the frontend on http://localhost:4000

Navigate to Sign up page, fill in the information to create new user.

After that you will be redirected to home page

Click on 'Create Expense' button to create new expense, type in amount, select category and date

Click on 'Create' to confirm and create Click on 'Close' to reject and close window

Once Expense Card is created to add new expenses to the existing category just click on 'Add Expense' button

Click on 'Create' to confirm and create Click on 'Close' to reject and close window

Change month by clicking on button with different month name Clik on Log out to close the session, after that you will be redirected to login page

Backend is running on http://localhost:3000/

Routes are defined in routes.rb file To see this routes in browser user must be logged in otherwise yoy will see "Not authorized" message

To see categories go to: http://localhost:3000/categories

To see infortmation about currently logged in user go to: http://localhost:3000/me

To see information about user's expenses go to: http://localhost:3000/users/user_id/expenses where user_id is a number http://localhost:3000/users/3/expenses

To see information about one expense for user go to http://localhost:3000/users/user_id/expenses:id which with data looks like: http://localhost:3000/users/3/expenses/45

Other routes are related witch create, update and destroy actions and can be triggered from Frontend:

create new user after submitting Sign up form

create new session after login

destroy session after log out

create new expense after clicking on 'Create Expense' and then 'Create' button

update expense after clicking on 'Add Expense' and then 'Create' button

destroy expense after clicking on 'Delete' button

This application has all the starter code needed to help you deploy your application to Heroku. It's recommended to deploy your project early and push up changes often to ensure that your code works equally well in production and development environments.

If you've already set up your environment to deploy to Heroku, you can run the commands below to deploy your application. If not, make sure to check out the Environment Setup section below.

To deploy, first log in to your Heroku account using the Heroku CLI:

heroku login

Create the new Heroku app:

heroku create my-app-name

Add the buildpacks for Heroku to build the React app on Node and run the Rails app on Ruby:

heroku buildpacks:add heroku/nodejs --index 1
heroku buildpacks:add heroku/ruby --index 2

To deploy, commit your code and push the changes to Heroku:

git add .
git commit -m 'Commit message'
git push heroku main

Note: depending on your Git configuration, your default branch might be named master or main. You can verify which by running git branch --show-current. If it's master, you'll need to run git push heroku master instead.

Any time you have changes to deploy, just make sure your changes are committed on the main branch of your repo, and push those changes to Heroku to deploy them.

You can view your deployed app with:

heroku open

Verify which version of Ruby you're running by entering this in the terminal:

ruby -v

Make sure that the Ruby version you're running is listed in the supported runtimes by Heroku. At the time of writing, supported versions are 2.6.8, 2.7.4, or 3.0.2. Our recommendation is 2.7.4, but make sure to check the site for the latest supported versions.

If it's not, you can use rvm to install a newer version of Ruby:

rvm install 2.7.4 --default

You should also install the latest versions of bundler and rails:

gem install bundler
gem install rails

Verify you are running a recent version of Node with:

node -v

If your Node version is not 16.x.x, install it and set it as the current and default version with:

nvm install 16
nvm use 16
nvm alias default 16

You can also update your npm version with:

npm i -g npm

You can sign up at for a free account at https://signup.heroku.com/devcenter.

Download the Heroku CLI. For OSX users, you can use Homebrew:

brew tap heroku/brew && brew install heroku

For WSL users, run this command in the Ubuntu terminal:

curl https://cli-assets.heroku.com/install.sh | sh

If you run into issues installing, check out the Heroku CLI downloads page for more options.

After downloading, you can login via the CLI in the terminal:

heroku login

This will open a browser window to log you into your Heroku account. After logging in, close the browser window and return to the terminal. You can run heroku whoami in the terminal to verify that you have logged in successfully.

Heroku requires that you use PostgreSQL for your database instead of SQLite. PostgreSQL (or just Postgres for short) is an advanced database management system with more features than SQLite. If you don't already have it installed, you'll need to set it up.

To install Postgres for WSL, run the following commands from your Ubuntu terminal:

sudo apt update
sudo apt install postgresql postgresql-contrib libpq-dev

Then confirm that Postgres was installed successfully:

psql --version

Run this command to start the Postgres service:

sudo service postgresql start

Finally, you'll also need to create a database user so that you are able to connect to the database from Rails. First, check what your operating system username is:

whoami

If your username is "ian", for example, you'd need to create a Postgres user with that same name. To do so, run this command to open the Postgres CLI:

sudo -u postgres -i

From the Postgres CLI, run this command (replacing "ian" with your username):

createuser -sr ian

Then enter control d or type logout to exit.

This guide has more info on setting up Postgres on WSL if you get stuck.

To install Postgres for OSX, you can use Homebrew:

brew install postgresql

Once Postgres has been installed, run this command to start the Postgres service:

brew services start postgresql

If you ran into any errors along the way, here are some things you can try to troubleshoot:

• If you're on a Mac and got a server connection error when you tried to run rails db:create, one option for solving this problem for Mac users is to install the Postgres app. To do this, first uninstall postgresql by running brew remove postgresql. Next, download the app from the Postgres downloads page and install it. Launch the app and click "Initialize" to create a new server. You should now be able to run rails db:create.

• If you're using WSL and got the following error running rails db:create:

  PG::ConnectionBad: FATAL:  role "yourusername" does not exist

  The issue is that you did not create a role in Postgres for the default user account. Check this video for one possible fix.

• If your app failed to deploy at the build stage, make sure your local environment is set up correctly by following the steps at the beginning of this lesson. Check that you have the latest versions of Ruby and Bundler, and ensure that Postgresql was installed successfully.

• If you deployed successfully, but you ran into issues when you visited the site, make sure you migrated and seeded the database. Also, make sure that your application works locally and try to debug any issues on your local machine before re-deploying. You can also check the logs on the server by running heroku logs.

For additional support, check out these guides on Heroku:

• Deploying a Rails 6 App to Heroku
• Rails Troubleshooting on Heroku