446 project command

[mtgoncalves1]

No description provided.

[mueschm]

This is definitely on the right track but there are some changes we should make.

1. Frontend, Backend, and Database are not the only types we allow. The point of these names is that if I ask for react for my project it should go to that template.json and get a list of elements to ask me for, that list could point to 10 other required service types all with unique names. This gives control over to the marketing and customer success team rather than having us update our code each time.
2. The source of truth should not be in the project. We should just let users pick any project name and then look to see if that project exists on Github to kick off the flow.
3. Looking at the way the databases work we may want to just allow custom architect.yml in the template.json file that just gets added directly into the generated architect.yml.

[mueschm]

So there is some high level things we should fix first, once those are done I will do another deep dive pass since these require some big code changes.

[mueschm]

This feels like we are getting very close!

[zach-j-dev]

@mueschm @tjhiggins Init command is ready to go and tested. As a quick note - put a PR for the config template , so the latest projects won't show in the selections until after it's merged (ASP, Ruby)

[TylerAldrich]

Couple small changes - also I noticed this has an empty creds.json committed. I think one of the tests always adds that empty file and we have it .gitignore'd in the tests/ directory, but it gets created wherever you run tests from... could you remove that file and add it to the .gitignore as well?

[TylerAldrich]

Code-wise everything looks good now, I just tried out the tool and noticed a couple things that are a bit misleading that we should reword:

? What should the name of the component be? test-comp

This doesn't seem to actually be the name of the component, but rather the folder that we create to clone the project into. I tested out cloning the Go project and I end up with a file structure like:

test-comp/
    go/
        architect.yml
        (other files...)

At the end, we then say:

To Deploy locally, run:
	$ architect dev test-comp/architect.yml

This isn't accurate because we create the test-comp folder, then clone the go project within it, so the real path would be architect dev test-comp/go/architect.yml (and would change for every project)

Perhaps what we should do to fix this is:

1. Change "What should the name of the component be" to something that indicates it's just naming a folder (like "what's the name of your project") OR actually modify the cloned architect.yml with the name chosen (the former is easier of course, probably a good starting place because we don't need to be too fancy)
2. We should run git clone <git repo url> . to clone into the folder we created so the file structure is:

test-comp/
    architect.yml
    (other files...)

With the updated clone command the final message won't be a lie and the dev command could be copy-pasta'd successfully

[TylerAldrich]

Realized Zach was out today so I fixed the things I suggested above

[zach-j-dev]

@TylerAldrich muchas gracias

[github-actions]

🎉 This PR is included in version 1.29.0 🎉

The release is available on:

• v1.29.0
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀