Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue on initial setup when running "task init" #8

Open
Dresse opened this issue Mar 8, 2024 · 0 comments
Open

Issue on initial setup when running "task init" #8

Dresse opened this issue Mar 8, 2024 · 0 comments

Comments

@Dresse
Copy link

Dresse commented Mar 8, 2024

I don't know if this is something that needs to be looked into or if it was just my computer being weird. But for good measures I decided to report this issue anyway.

When setting up dapple, by running task init I encountered 2 separate issues the first 2 times. The third time I had to delete already created folders and on the fourth attempt everything when smoothly:

  1. Run I got the standard "approve the authenticity of host github.com" for the repositories (even though I have all 3 repositories cloned separately in their own folders. I accepted but then the whole task init process stopped. I waited 5 minutes and exited the task myself.

  2. The second time I ran the task, dpl-cms was cloned into /cms folder, the /react and /design-system folders was also created, but the repositories was not cloned into them. The whole process got stuck when the task was running this command:

task: [cms:clone] sed "s|COMPOSE_PROJECT_NAME=dpl-cms|COMPOSE_PROJECT_NAME=dapple-cms|g" <cms/.env.example >cms/.env

After some waiting time, I exited the task myself.

On the third attempt it exited when trying to clone into /cms folder as it was not empty. I deleted the 3 folders and ran the command again for the fourth time. This time the task finished and all 3 repositories was cloned into their separate folders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant