Spring Boot Application Multidatasource/Starter-Project

The only thing better than a Maven archetype is a repo you can fork with everything already setup to speed up the creation of new Spring Boot based Web applications, just fork-and-code.

This repository contains a recipe/scaffolding for bootstrapping a Monolithic Web Application with the features & Technology stack listed below. Delete the sample code (or keep it.) and add your own, you’re good to go.

Essentially it's a simple on-demand application backend for rapd-prototyping.

Features include but not limited to:

• [Multidatasource]

_{Built with ❤︎ by Vaibhav J and contributors}

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

Kindly refer to CONTRIBUTING.md for important Pull Request Process details

1. In the top-right corner of this page, click Fork.

2. Clone a copy of your fork on your local, replacing YOUR-USERNAME with your Github username.

   git clone https://github.com/YOUR-USERNAME/Spring-Boot-Application-Template.git

3. Create a branch:

   git checkout -b <my-new-feature-or-fix>

4. Make necessary changes and commit those changes:

   git add .

   git commit -m "new feature or fix"

5. Push changes, replacing <add-your-branch-name> with the name of the branch you created earlier at step #3. :

   git push origin <add-your-branch-name>

6. Submit your changes for review. Go to your repository on GitHub, you'll see a Compare & pull request button. Click on that button. Now submit the pull request.

That's it! Soon I'll be merging your changes into the master branch of this project. You will get a notification email once the changes have been merged. Thank you for your contribution.

Kindly follow Conventional Commits to create an explicit commit history. Kindly prefix the commit message with one of the following type's.

build : Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci : Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
docs : Documentation only changes
feat : A new feature
fix : A bug fix
perf : A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style : Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
test : Adding missing tests or correcting existing tests

The End

In the end, I hope you enjoyed the application and find it useful, as I did when I was developing it to create a Spring Boot web application template with good/convenient practices for rapid prototyping.

If you would like to enhance, please:

• Open PRs,

• Give feedback,

• Add new suggestions, and

• Finally, give it a 🌟.

• Happy Coding ...* 🙂