Docker error during cloned github about cli HOT 15 CLOSED

Hey! 👋 Thanks for opening your first issue here! Be sure to follow the issue template.

from cli.

Hi,

Did you try to install git on your PC?

from cli.

from cli.

Create project backend...
[OK] Backend: created with the github.com/create-go-app/fiber-go-template template!

• Create project frontend...
  [ERROR]
  root@quirky-turing:~/

from cli.

Please try all of this via native Go installation:

go install github.com/create-go-app/cli/v4/cmd/cgapp@latest

from cli.

i try see the result , thanks for reply

from cli.

please see this..
and please do this same test in a new server
so you can exactly understand the error .

from cli.

Mr koddr ??
You create go cli it was very good , but pls fix this error , if some new one is try to do so this will gives error...
They unable to create frontend and backend.

from cli.

I try cgapp in local go environment over server and also in docker their is a error , comming in both and that is because , Docker cgapp -v and cgapp -v is same in both environment .
That mean their is error in cgapp git clonning function. Thats why both env shows error..
pls fix that ..

from cli.

from cli.

When tested (macOS 13 on M1 and Fedora Linux 37), none of the errors you point out were found.

Here is a screenshot of the project being created correctly (native Go installation):

This error when using a Docker container:

Error: [ERROR][ERROR]Repository `github.com/create-go-app/*-go-template` was not cloned!

Can occur in very different situations that can (and will) be unique to your PC. For example, your system user does not have enough permissions to create a backend folder on your system to copy the Fiber template.

Please check this.

✨ I realize that it's difficult and confusing when only you are getting errors when everyone else's CLI is running normally without fail. But you should also realize that this is an Open Source and Non-profit project that comes "AS IS".

❗️ If something doesn't work on your PC, it means that the problem is not in the CLI, but in your workstation. That sounds logical, doesn't it? So please be understanding.

from cli.

from cli.

First, I don't use AWS (or else) in my work (or home).

Second, if you do use it, you are free to do a test on your instance. Then I will gladly wait for your PR with edits to the tests in this repository exclusively for deploy on AWS (or else), which I will include in the next patch version of the CLI.

Third, for the tests to work, you must have all the necessary containers (e.g. Postgres) running on your machine, as the tests use database/cache/etc connections.

from cli.