refactor(site): remove name argument from site:deploy

The `name` argument for the `site:deploy` command is no longer needed as the site name is now derived from the `--subdomain` option or generated randomly. This change simplifies the command's signature and updates the corresponding help documentation.

BREAKING CHANGE: The positional `name` argument has been removed from the `site:deploy` command.

Author: bitsnaps

bin/index.js

@@ -67,7 +67,6 @@ async function main() {
   program
     .command('site:deploy')
     .description('Deploy a local web project to Puter')
-    .argument('[name]', 'Name of the site')
     .argument('[remoteDir]', 'Remote directory path')
     .option('--subdomain <subdomain>', 'Subdomain for the site')
     .action(async (name, remoteDir, options) => {

src/executor.js

@@ -156,8 +156,7 @@ const commands = {
  * @param {string} input The command line input
  */
 export async function execCommand(context, input) {
-  const [cmd, ...args] = input.split(' ');
-
+  const [cmd, ...args] = input?input.split(' '):[];
 
   // Add the command to history (skip the "history" command itself)
   if (cmd !== 'history') {
@@ -355,9 +354,9 @@ function showHelp(command) {
       Example: site:create mywebsite /path/to/dir --subdomain=mywebsite
     `,
     'site:deploy': `
-      ${chalk.cyan('site:deploy [<valid_name_app>] [<remote_dir>] [--subdomain=<subdomain>]')}
+      ${chalk.cyan('site:deploy [<remote_dir>] [--subdomain=<subdomain>]')}
       Deploy a local web project to Puter.
-      Example: site:deploy my-app ./my-app --subdomain my-app
+      Example: site:deploy ./my-app --subdomain my-app
     `,
     '!': `
       ${chalk.cyan('!<command>')}