- π About the Project
- π» Getting Started
- π₯ Authors
- π Future Features
- π€ Contributing
- βοΈ Show your support
- π Acknowledgements
- β FAQ (OPTIONAL)
- π License
This is a simple project created as an api endpoint that randomly displays different greetings. The objective of this project is to learn how to create rails as an api endpoint.
hello-rails-backend Randomly display different greetings
Client
Server
Database
- Displays greetings
Add a link to your deployed project.
-
Link to the react-app: https://github.com/kessio/hello-rails-front-end.git
-
No live demo
To get a local copy up and running, follow these steps.
In order to run this project you need:
- ruby
- Rails
- npm
- postgresql
Clone this repository to your desired folder:
cd my-folder
git clone https://github.com/kessio/hello-rails-backend.git
Install this project with:
cd my-project
bundle install
npm install
To run the project, execute the following command:
rails server
There are no tests to run for this project
You can deploy this project using:
Mention all of the collaborators of this project.
π€ Sharon Kessio
- GitHub: @kessio
- Twitter: @kessio_sharon
- LinkedIn: LinkedIn
Describe 1 - 3 features you will add to the project.
- Add gretings
Contributions, issues, and feature requests are welcome!
Feel free to check the issues page.
If you like this project leave a star on this repository
- Thanks to everyone who made this project a success
Add at least 2 questions new developers would ask when they decide to use your project.
-
What is the difference between using rake and rails?
- Rails core team decided to have consistency by enabling rails command to support everything that rake does.
For example in Rails 5 commands like db:migrate, db:setup, db:test etc which are part of rake command in Rails 4 are now being supported by rails command. However you can still choose to use rake to run those commands similar to how they were run in Rails 4. This is because Rails community has introduced Rake Proxy instead of completely moving the command options from rake to rails.
What happens internally is that when rails db:migrate command is executed, Rails checks if db:migrate is something that rails natively supports or not. In this case db:migrate is not natively supported by rails, so Rails delegates the execution to Rake via Rake Proxy.
If you want to see all the commands that is supported by rails in Rails 5 then you can get a long list of options by executing rails --help.
- What's new in Rails version 7
- This article explain what's new with Ruby on rail version 7
This project is MIT licensed.