Iced-Latte
[](https://github.com/Sunagatov/Iced-Latte/actions) [](https://github.com/danilqa/node-file-router/blob/main/LICENSE) [](https://github.com/Sunagatov/Iced-Latte/issues) [](https://github.com/Sunagatov/Iced-Latte) [](https://app.codecov.io/github/Sunagatov/Iced-Latte) [](https://hub.docker.com/r/zufarexplainedit/iced-latte-backend/) [](https://github.com/Sunagatov/Iced-Latte/graphs/contributors) [](https://github.com/Sunagatov/Iced-Latte/stargazers) [](https://github.com/Sunagatov/Iced-Latte/network/members)Table of Contents
Introduction
π₯ Iced-Latte (Backend) is a non-profit sandbox project where a team of IT enthusiasts are working on creating a modern marketplace (https://iced-latte.uk/) for selling coffee in order to pump up their soft and hard skills and have fun working on an interesting project.
π₯ It's crucial to note that we operate without financial support from any party, and we don't compensate anyone financially either. Our efforts are fuelled solely by passion and dedication.
π₯ Github-Stars π₯
Please support Iced Latte project by Giving Stars π on Github repositories - your ratings mean a lot to us!π
Tech Stack
- Architecture: Monolith.
- Computer language: Java 17.
- Framework: Spring Web, Spring Boot 3, Spring Data, Spring Security, Spring Actuator, Spring Web, Spring Retry, Lombok, Apache Commons, Spring Mail, Google Guava.
- Security: JWT, TLS.
- Migration tool: Liquabase.
- Logging: Log4j2, Slf4j.
- Unit Tests: JUnit 5.
- E2E Tests: Rest Assured, Test containers.
- Converter: Mapstruct.
- Test coverage: Jacoco.
- API Specs: Open API + Spring Docs.
- Validation: Javax validation.
Quick Start
Follow the setup instructions in START.MD to get the project up and running.
π’ Deployment
No k8s, no AWS, we ship dockers directly via ssh and it's beautiful!
The entire production configuration is described in the docker-compose.local.yml file.
Then, Github Actions have to take all the dirty work. They build, test and deploy changes to production on every merge to master (only official maintainers can do it).
Explore the whole .github folder for more insights.
We're open for proposals on how to improve our deployments.
π€ Forking and tweaking
Forks are welcome.
Three huge requests for everyone:
- Please share new features you implement with us, so other folks can also benefit from them, and your own codebase minimally diverges from the original one (so you can sync updates and security fixes) .
- Do not use our issues and other official channels as a support desk. Use chats.
πββοΈ How to report a bug?
- π Open a new issue.
- π¦ Please, use a search, to check, if there is already existed issue!
- Explain your idea or proposal in all the details:
- Make sure you clearly describe "observed" and "expected" behaviour. It will dramatically save time for our contributors and maintainers.
- For minor fixes please just open a PR.
π Now to propose a new feature?
- Go to our Discussions
- Check to see if someone else has already come up with the idea before
- Create a new discussion
- πΌ If it's UI/UX related: attach a screenshot or wireframe
π Contributions
Contributions are welcome.
The main point of interaction is the Issues page.
The official development language at the moment is English, because 100% of our users speak it. We don't want to introduce unnecessary barriers for them. But we are used to writing commits and comments in Russian and we won't mind communicating with you in it.
The bussiness docs are here Docs.
Swagger REST APIs contracts described here.
π I want to write some code
- Open our Issues page to see the most important tickets at top.
- Pick one issue you like and leave a comment inside that you're getting it.
For big changes open an issues first or (if it's already opened) leave a comment with brief explanation what and why you're going to change. Many tickets hang open not because they cannot be done, but because they cause many logical contradictions that you may not know. It's better to clarify them in comments before sending a PR.
π¦Pay attention to issue labels!
π© Ready to implement
- good first issue β good tickets for first-timers. Usually these are simple and not critical things that allow you to quickly feel the code and start contributing to it.
- bug β if something is not working, it needs to be fixed, obviously.
- high priority β the first priority tickets.
- enhancement β accepted improvements for an existing module. Like adding a sort parameter to the feed. If improvement requires UI, be sure to provide a sketch before you start.
π¨ Discussion is needed
- new feature β completely new features. Usually they're too hard for newbies, leave them for experienced contributors.
- idea β discussion is needed. Those tickets look adequate, but waiting for real proposals how they will be done. Don't implement them right away.
π₯ Questionable
- Β―\(γ)\/Β― - special label for questionable issues. (should be closed in 60 days of inactivity)
- [no label] β ticket is new, unclear or still not reviewed. Feel free to comment it but wait for our maintainers' decision before starting to implement it.
π Our top contributors
Take some time to press F and give some respects to our best contributors, who spent their own time to make the club better.
π Iced Latte project creator / Product owner / Tech Lead
π Project manager
π΅οΈββοΈ QA engineers
βοΈ Backend developers
π₯οΈ Frontend developers
π¨ UX/UI designers
π Business and system analysts
Let's press F to pay respects to these awesome contributors!
π©βπΌ License
In other words, you can use the code for private and commercial purposes with an author attribution (by including the original license file or mentioning the Iced-Latte project).
π Contact (Community and Support)
Join our IT community Zufar Explained IT on Telegram.
Feel free to contact us via email: zufar.sunagatov@gmail.com.
β€οΈ