Create Go App

Hello, friends! 😉 Today, I'd like to present you my CLI for automation many things for starting a new project. I called it Create Go App (or CGAPP for short). The main idea was to create a universal tool for full automation of the project start when you don't need to install everything you need separately.

Wow! So much support, I was surprised. Thanks! 🤗 Now I'd like to tell you a little more about this project and about myself. The project originally developed by me for my friends who write a lot in Node.js on the backend and would like to try the Go programming language (or even switch to it in the future). In the JavaScript world, there are many handy tools to deploy a finished project in just two clicks. My project is an attempt to make the same tool, but for Go. Probably you think that Create Go App CLI is a “black box” that magically creates objects out of thin air. But that's not really true. The whole project built on UNIX principles that each element must have a clear function that it does well. So, basically, the CLI contains three main parts: 1. Pre-configured backend part; 2. Frontend part generated by Vite.js; 3. Deploy-ready Ansible roles; I hope it helps you understand Create Go App. And now a bit about me 😉 I am a software engineer with more than 12 years of practical experience in developing websites and web applications of different complexity and purpose. It's not just the code and layout. This includes UX and system design, CJM, and sleepless nights over the product roadmap. Also, I keep my blog (or in-flight magazine) at Dev.to, where I regularly highlight my activities, or rather, the useful insights I've learned from the next task/project/etc. Just there are a few introductory articles on Create Go App CLI and ecosystem: — https://dev.to/koddr/a-powerful-... — https://dev.to/koddr/what-s-new-... — https://dev.to/koddr/the-create-...

Hey! Hello! I'm really amazed at how many people have found my Create Go App project helpful and important to their development process. This is truly motivating, thank you so much. I would like to draw your attention to one point that has to do with the production-ready Fiber and net/http templates. They use the swaggo/swag package to generate Swagger documentation for endpoints. It's a very nice package with good support. But with recent updates, my strict CI started throwing bugs. This is because there is a lot of code in this package that exists for backward compatibility with go1.15 (both stylistically and just deprecated). I've sent a PR fixing these bugs (here it is: https://github.com/swaggo/swag/p...). But the contributors can't accept them, as doing so might break backward compatibility with earlier versions of Go. I've offered various solutions to this problem, but so far, I've received nothing in response apart from “it's an open-source project”. If any of my subscribers would like to help with this problem and become a contributor to the popular Swagger documentation generation package, then unsubscribe directly in that PR of mine, please. I'm certain that together we can solve this problem. 😉