This repository contains a fullstack application with separate frontend and backend directories. The project uses the following technologies:
- Backend: Node.js, Express, MongoDB (or any other database)
- Frontend: React (or any other frontend framework)
The application is designed to be modular, scalable, and follows best practices for both frontend and backend development.
fullstack-app/
├── backend/ # Backend architecture using Node.js and Express
├── frontend/ # Frontend architecture using React
├── README.md # General documentation of the projectThe backend is built using Node.js and Express. It follows a modular architecture, with the logic separated into controllers, routes, services, and models. The backend communicates with a MongoDB database and exposes a RESTful API.
For more details about the backend structure and setup, check the backend README.
The frontend is built using React. It follows a component-based architecture and communicates with the backend API to fetch and display data.
For more details about the frontend structure and setup, check the frontend README.
-
Clone the repository:
git clone https://github.com/foucsi/fullstack-app.git
-
Navigate to the backend folder and install dependencies:
cd fullstack-app/backend npm install -
Navigate to the frontend folder and install dependencies:
cd ../frontend npm install
-
Backend: To start the backend server, navigate to the backend directory and run:
cd backend npm start -
Frontend: To start the frontend development server, navigate to the frontend directory and run:
cd frontend npm start -
The backend server runs on
http://localhost:5000by default, and the frontend onhttp://localhost:3000. The frontend will communicate with the backend using RESTful APIs.
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We Use Github Flow, So All Code Changes Happen Through Pull Requests
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can.
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports. I'm not even kidding.
- 2 spaces for indentation rather than tabs
- You can try running
npm run lintfor style unification
Coming soon
We greatly appreciate everyone who contributes to fullstack-app! Your commitment and creativity make this project what it is. To express our gratitude, we will:
- Mention all contributors in our CONTRIBUTORS.md file
- Regularly share updates about significant contributions on our social media channels (Twitter, LinkedIn, etc.)
- Highlight the most active contributors on our website and in our newsletters
- Offer regular contributors the opportunity to become project maintainers
Join us in this open-source journey and become part of our growing community!
Thanks to the following contributor for their work on this project:
|
Julien Foucart 💻 Code and 📖 Documentation |