Consider using a CLI tool to get started

[damiensedgwick]

Hey, firstly, great project!

I am the creator of Napp which is a similar project in the sense that it aims to aid developers create projects using Golang / TailwindCSS and other minimal tools (I went with HTMX instead of Alpine) and I didn't use Templ due to issues with Golang!

After coming across your project on Reddit, I decided to give it a look and noticed that to get started, a user has to clone your repo and then make changes and then do some installation steps etc.

It could be a nice enhancement, to utilise a CLI tool much like I did for Napp so that a user can install the tool and have it do all of the creation process. The benefits this would bring would be

• No internet access required to create the project (installing deps would still need this however)
• I suspect it will be quicker than cloning and changing changes.
• You would be able to use a cool command such as goat init

Anyway, this is just a out there thought but I would be happy to talk it through with you some more if you would like!

[morethancoder]

Hey, thanks for checking out the project and for your great suggestion! I'm actually already working on a CLI tool that does exactly what you described and even more.

GOAT CLI designed to:

• Create starter projects
• Let you choose between static or dynamic rendering
• Manage routing
• Automatically configure handlers & middleware for SSR apps
• Come with a config for commands like watch and serve/run

I'm using Cobra for the CLI structure. If you have experience with Cobra or similar CLI tools, I'd really appreciate the collaboration! Your idea about goat init is great and fits perfectly with what I'm aiming for. Would you be interested in discussing this further? I'd love to hear more about your experiences with Napp and maybe we could exchange some ideas on CLI tool development for Go web projects.

[damiensedgwick]

Hey, the GOAT CLI sounds really cool with what you have planned for it!

I haven't used Cobra personally, I did consider it in the beginning however I decided to go with cli in the end because it seemed a better / lighter use case in my scenario.

I'd definitely be up for discussing it further and collaborating on it, entirely up to you in regards to where and when! Just let me know!