Welcome to the Fullstack Boilerplates repository! This project aims to provide easy-to-use boilerplates for various fullstack stacks, helping engineers kickstart their projects without the usual setup hassle.
Starting a new project often involves a lot of repetitive setup tasks: configuring servers, setting up databases, integrating frontend and backend, and more. Our goal is to simplify this process by providing ready-made boilerplates for common fullstack stacks, so you can focus on building features rather than setting up infrastructure.
As an experienced developer, I've faced the pain of repeatedly setting up projects from scratch. I realized that many developers could benefit from a standardized, well-documented starting point for their fullstack applications. This repository is the result of our efforts to create a resource that can save time and reduce setup errors.
Each boilerplate includes a fully configured stack with Docker support. This means you'll have a consistent environment for development, testing, and deployment.
We are continuously adding new stacks. Currently, you can find branches for:
Simply clone the repository and checkout the branch for the stack you need. Follow the steps in the Getting Started section below.
Absolutely! We welcome contributions. Feel free to open issues or submit pull requests to add new stacks or improve existing ones.
You can find more details on how to contribute here
!!important
Make sure to create the .env file and put the content from .env.example
Follow these steps to get started with a boilerplate:
- Clone the Repository
https://github.com/sharukhkhanajm/fullstack-boilerplates.git
cd fullstack-boilerplates
- Checkout the Desired Branch
git checkout Go-React-Postgres
-
Set Up Docker Make sure you have Docker installed on your machine. If not, download and install it from here.
-
Start the Containers
For development
docker compose -f docker-compose.dev.yml up --build
For Production
docker compose up --build
- Update the host file
If we put https://auth.localhost in the browser it's not gonna know it should resolve to localhost so for that we need to modify the host file
for Mac users
sudo nano /etc/hosts
Now add these lines
127.0.0.1 auth.localhost
127.0.0.1 api.auth.localhost
for Windows users
please update Windows users
Save the file
- Access the Application Once the containers are up, you can access the application at https://auth.localhost (or another specified port, depending on the stack).
- Open your caddy container
- Look for
root.crtfile
- Right click and save the file on your local machine
for Mac users
- Open Keychain Access and click on System
- Go to file -> import items and import the
root.crtfile
- To trust this certificate double click on it and change it to always trust
for Windows users
please update Windows users
For any questions or suggestions, feel free to reach out via GitHub issues or contact at https://x.com/iamsharukh_khan
Happy coding!