chore: wip

Author: chrisbbreuer

.gitignore

@@ -13,3 +13,5 @@ docs/.vitepress/cache
 /test/.tmp
 bin/gitit
 bin/gitit*
+/my-stack
+/stack-example

README.md

@@ -30,26 +30,26 @@ Gitit comes with the following features:
 bun install -g @stacksjs/gitit
 
 # or use directly with bunx
-bunx @stacksjs/gitit template github:user/repo my-project
+bunx @stacksjs/gitit github:user/repo my-project
 ```
 
 ## Usage
 
 ```bash
 # Basic usage
-gitit template github:user/repo my-project
+gitit github:user/repo my-project
 
 # With options
-gitit template github:user/repo my-project --install --shell
+gitit github:user/repo my-project --install --shell
 
 # Clone with custom command
-gitit template github:user/repo my-project --command "npm run dev"
+gitit github:user/repo my-project --command "npm run dev"
 
 # Use offline cached template
-gitit template github:user/repo my-project --offline
+gitit github:user/repo my-project --offline
 
 # Clone to a specific directory
-gitit template github:user/repo ./path/to/project
+gitit github:user/repo ./path/to/project
 ```
 
 ## Available Options

bin/cli.ts

@@ -1,8 +1,11 @@
 import type { GitItOptions } from '../src/types'
+import { spawn } from 'node:child_process'
 import { relative } from 'node:path'
 import process from 'node:process'
 import { CAC } from 'cac'
 import { version } from '../package.json'
+import { downloadTemplate } from '../src/gitit'
+import { startShell } from '../src/utils'
 
 const cli = new CAC('gitit')
 
@@ -42,22 +45,55 @@ cli
       process.chdir(options.cwd)
     }
 
-    // Placeholder for actual template download logic
-    const templateDir = dir || './'
-    const _to = relative(process.cwd(), templateDir) || './'
-    console.log(`✨ Successfully cloned to \`${_to}\`\n`)
+    try {
+      // Use the actual downloadTemplate function instead of placeholder
+      const result = await downloadTemplate(template, {
+        dir,
+        force: options?.force,
+        forceClean: options?.forceClean,
+        offline: options?.offline,
+        preferOffline: options?.preferOffline,
+        auth: options?.auth,
+        install: options?.install,
+      })
 
-    // Open a shell if requested
-    if (options?.shell) {
-      console.log('Opening shell in cloned directory...')
-      // Placeholder for shell opening logic
-    }
+      const _to = relative(process.cwd(), result.dir) || './'
+      console.log(`✨ Successfully cloned to \`${_to}\`\n`)
+
+      // Open a shell if requested
+      if (options?.shell) {
+        startShell(result.dir)
+      }
+
+      // Run custom command if specified
+      if (options?.command) {
+        console.log(`Running command: ${options.command}`)
 
-    // Run custom command if specified
-    if (options?.command) {
-      console.log(`Running command: ${options.command}`)
-      // Placeholder for command execution
-      console.log(`Command execution would happen here`)
+        // Execute the command
+        const [cmd, ...args] = options.command.split(' ')
+        const child = spawn(cmd!, args, {
+          cwd: result.dir,
+          stdio: 'inherit',
+          shell: true,
+        })
+
+        // Wait for the command to finish
+        await new Promise<void>((resolve, reject) => {
+          child.on('close', (code) => {
+            if (code === 0) {
+              resolve()
+            }
+            else {
+              reject(new Error(`Command exited with code ${code}`))
+            }
+          })
+          child.on('error', reject)
+        })
+      }
+    }
+    catch (error) {
+      console.error(`Error cloning template: ${error instanceof Error ? error.message : String(error)}`)
+      process.exit(1)
     }
   })
 

docs/advanced/authentication.md

@@ -9,14 +9,14 @@ Gitit supports authentication for private repositories across different provider
 The most common authentication method is using personal access tokens:
 
 ```bash
-gitit template github:user/private-repo my-project --auth "your-access-token"
+gitit github:user/private-repo my-project --auth "your-access-token"
 ```
 
 You can also provide authentication via environment variables:
 
 ```bash
 export GITIT_AUTH="your-access-token"
-gitit template github:user/private-repo my-project
+gitit github:user/private-repo my-project
 ```
 
 The environment variable `GITIT_AUTH` is checked by default if no `--auth` parameter is provided.
@@ -34,7 +34,7 @@ Authorization: Bearer your-access-token
 For GitHub, you need a [Personal Access Token (PAT)](https://github.com/settings/tokens):
 
 ```bash
-gitit template github:user/private-repo my-project --auth "ghp_xxxxxxxxxxxxxxx"
+gitit github:user/private-repo my-project --auth "ghp_xxxxxxxxxxxxxxx"
 ```
 
 GitHub API calls use the following headers:
@@ -50,23 +50,23 @@ X-GitHub-Api-Version: 2022-11-28
 For GitLab, you need a [Personal Access Token](https://gitlab.com/-/profile/personal_access_tokens):
 
 ```bash
-gitit template gitlab:user/private-repo my-project --auth "glpat-xxxxxxxxxxxxxxx"
+gitit gitlab:user/private-repo my-project --auth "glpat-xxxxxxxxxxxxxxx"
 ```
 
 ### Bitbucket
 
 For Bitbucket, you need an [App Password](https://bitbucket.org/account/settings/app-passwords/):
 
 ```bash
-gitit template bitbucket:user/private-repo my-project --auth "your-app-password"
+gitit bitbucket:user/private-repo my-project --auth "your-app-password"
 ```
 
 ### SourceHut
 
 For SourceHut, use your [OAuth token](https://meta.sr.ht/oauth):
 
 ```bash
-gitit template sourcehut:user/private-repo my-project --auth "your-oauth-token"
+gitit sourcehut:user/private-repo my-project --auth "your-oauth-token"
 ```
 
 ## Custom GitHub or GitLab Instances
@@ -76,11 +76,11 @@ If you're using a GitHub Enterprise or custom GitLab instance, you can set the A
 ```bash
 # For GitHub Enterprise
 export GITIT_GITHUB_URL="https://github.your-company.com/api/v3"
-gitit template github:user/private-repo my-project
+gitit github:user/private-repo my-project
 
 # For GitLab self-hosted
 export GITIT_GITLAB_URL="https://gitlab.your-company.com"
-gitit template gitlab:user/private-repo my-project
+gitit gitlab:user/private-repo my-project
 ```
 
 ## Secure Authentication Practices
@@ -118,7 +118,7 @@ jobs:
     steps:
       - uses: actions/checkout@v3
       - name: Clone template
-        run: gitit template github:user/private-repo my-project
+        run: gitit github:user/private-repo my-project
         env:
           GITIT_AUTH: ${{ secrets.GITHUB_TOKEN }}
 ```

docs/advanced/bitbucket-private-repos.md

@@ -19,7 +19,7 @@ Bitbucket uses App Passwords for API authentication. To create one:
 3. Select **Personal settings** from the menu
 4. In the left sidebar, click on **App passwords**
 5. Click the **Create app password** button
-6. Give your app password a descriptive name (e.g., "Gitit Template Access")
+6. Give your app password a descriptive name (e.g., "gitit Access")
 7. Select the following permissions:
    - **Repository**: Read
    - **Pull requests**: Read (optional)
@@ -31,7 +31,7 @@ Bitbucket uses App Passwords for API authentication. To create one:
 Once you have your app password, you can use it to clone private repositories:
 
 ```bash
-gitit template bitbucket:username/private-repo my-project --auth "your-app-password"
+gitit bitbucket:username/private-repo my-project --auth "your-app-password"
 ```
 
 Replace:
@@ -46,7 +46,7 @@ For security and convenience, you can set your app password as an environment va
 
 ```bash
 export GITIT_AUTH="your-app-password"
-gitit template bitbucket:username/private-repo my-project
+gitit bitbucket:username/private-repo my-project
 ```
 
 Add this to your `.bashrc`, `.zshrc`, or equivalent shell configuration file for persistent access.
@@ -84,23 +84,23 @@ If you get authentication errors:
 To clone a specific branch from a private Bitbucket repository:
 
 ```bash
-gitit template bitbucket:username/private-repo#develop my-project --auth "your-app-password"
+gitit bitbucket:username/private-repo#develop my-project --auth "your-app-password"
 ```
 
 ### Cloning Subdirectories
 
 To clone only a specific subdirectory from a private repository:
 
 ```bash
-gitit template bitbucket:username/private-repo/path/to/directory my-project --auth "your-app-password"
+gitit bitbucket:username/private-repo/path/to/directory my-project --auth "your-app-password"
 ```
 
 ### Combined Branch and Subdirectory
 
 You can specify both a branch and a subdirectory:
 
 ```bash
-gitit template bitbucket:username/private-repo/path/to/directory#develop my-project --auth "your-app-password"
+gitit bitbucket:username/private-repo/path/to/directory#develop my-project --auth "your-app-password"
 ```
 
 ## Configuration File
@@ -129,7 +129,7 @@ jobs:
     steps:
       - uses: actions/checkout@v3
       - name: Clone Bitbucket template
-        run: gitit template bitbucket:username/private-repo my-project
+        run: gitit bitbucket:username/private-repo my-project
         env:
           GITIT_AUTH: ${{ secrets.BITBUCKET_APP_PASSWORD }}
 ```

docs/advanced/custom-templates.md

@@ -83,7 +83,7 @@ This configuration file defines the template's metadata, variables, and lifecycl
 You can use custom templates just like any other template with Gitit:
 
 ```bash
-gitit template github:username/my-custom-template new-project
+gitit github:username/my-custom-template new-project
 ```
 
 If your template includes variables, you'll be prompted to provide values during the creation process.
@@ -93,7 +93,7 @@ If your template includes variables, you'll be prompted to provide values during
 You can also use local template directories:
 
 ```bash
-gitit template ./path/to/local/template new-project
+gitit ./path/to/local/template new-project
 ```
 
 This is useful during template development or for templates not hosted in a Git repository.
@@ -104,7 +104,7 @@ To share your custom templates with others:
 
 1. Push your template repository to a Git hosting service
 2. Share the template URL with your team or community
-3. Consider adding your template to the Gitit template registry (forthcoming feature)
+3. Consider adding your template to the gitit registry (forthcoming feature)
 
 ## Best Practices
 

docs/advanced/github-private-repos.md

@@ -20,7 +20,7 @@ To access private repositories, you'll need a Personal Access Token:
 4. Scroll down to the bottom of the left sidebar and click on **Developer settings**
 5. Click on **Personal access tokens** → **Tokens (classic)**
 6. Click **Generate new token** → **Generate new token (classic)**
-7. Give your token a descriptive name (e.g., "Gitit Template Access")
+7. Give your token a descriptive name (e.g., "gitit Access")
 8. Select the following scopes:
    - **repo** (Full control of private repositories)
    - **read:packages** (Optional - if you need to access template packages)
@@ -32,7 +32,7 @@ To access private repositories, you'll need a Personal Access Token:
 Once you have your personal access token, you can use it to clone private repositories:
 
 ```bash
-gitit template github:username/private-repo my-project --auth "ghp_your_token_here"
+gitit github:username/private-repo my-project --auth "ghp_your_token_here"
 ```
 
 Replace:
@@ -47,7 +47,7 @@ For security and convenience, you can set your token as an environment variable:
 
 ```bash
 export GITIT_AUTH="ghp_your_token_here"
-gitit template github:username/private-repo my-project
+gitit github:username/private-repo my-project
 ```
 
 Add this to your `.bashrc`, `.zshrc`, or equivalent shell configuration file for persistent access.
@@ -91,31 +91,31 @@ If you're using GitHub Enterprise, you can set a custom API URL:
 
 ```bash
 export GITIT_GITHUB_URL="https://github.your-company.com/api/v3"
-gitit template github:username/private-repo my-project --auth "your-token"
+gitit github:username/private-repo my-project --auth "your-token"
 ```
 
 ### Specifying Branches
 
 To clone a specific branch from a private GitHub repository:
 
 ```bash
-gitit template github:username/private-repo#develop my-project --auth "your-token"
+gitit github:username/private-repo#develop my-project --auth "your-token"
 ```
 
 ### Cloning Subdirectories
 
 To clone only a specific subdirectory from a private repository:
 
 ```bash
-gitit template github:username/private-repo/path/to/directory my-project --auth "your-token"
+gitit github:username/private-repo/path/to/directory my-project --auth "your-token"
 ```
 
 ### Combined Branch and Subdirectory
 
 You can specify both a branch and a subdirectory:
 
 ```bash
-gitit template github:username/private-repo/path/to/directory#develop my-project --auth "your-token"
+gitit github:username/private-repo/path/to/directory#develop my-project --auth "your-token"
 ```
 
 ## Configuration File
@@ -144,7 +144,7 @@ jobs:
     steps:
       - uses: actions/checkout@v3
       - name: Clone GitHub template
-        run: gitit template github:username/private-repo my-project
+        run: gitit github:username/private-repo my-project
         env:
           GITIT_AUTH: ${{ secrets.GITHUB_TOKEN }}
 ```
@@ -167,7 +167,7 @@ If you're using GitHub CLI (`gh`), you can create a token and use it directly:
 gh auth token
 
 # Use the token with gitit
-gitit template github:username/private-repo my-project --auth "$(gh auth token)"
+gitit github:username/private-repo my-project --auth "$(gh auth token)"
 ```
 
 This approach avoids storing the token in your environment or files.

docs/advanced/plugins.md

@@ -156,7 +156,7 @@ providers: {
 This would allow users to use templates with:
 
 ```bash
-gitit template myCompany:template-name my-project
+gitit myCompany:template-name my-project
 ```
 
 ## Plugin Configuration

docs/config.md

@@ -81,7 +81,7 @@ export default config
 _Then run:_
 
 ```bash
-gitit template github:user/repo my-project
+gitit github:user/repo my-project
 ```
 
 To learn more, head over to the [documentation](https://gitit.sh/).