mygensite 1.2.0 → 1.3.0

package/README.en.md

@@ -301,11 +301,32 @@ const site = await mygensite.deploy({
   access: 'public',
   files: [
     { name: 'index.html', content: '<h1>Hello World</h1>' },
-    { name: 'style.css', content: 'body { font-family: sans-serif; }' },
+    { name: 'assets/style.css', content: 'body { font-family: sans-serif; }' },
   ],
 });
 ```
 
+#### Deploy with curl
+
+Multipart `filename` strips directory paths (e.g. `assets/style.css` becomes `style.css`). Use the `filepaths` JSON field to preserve directory structure:
+
+```bash
+# Flat files (no subdirectories) — filepaths not needed
+curl -X POST https://mygen.site/api/deploy \
+  -F slug=demo -F access='{"mode":"public"}' \
+  -F files=@index.html -F files=@style.css
+
+# With subdirectories — filepaths required
+curl -X POST https://mygen.site/api/deploy \
+  -F slug=demo -F access='{"mode":"public"}' \
+  -F 'filepaths=["index.html","assets/style.css","assets/js/app.js"]' \
+  -F files=@index.html \
+  -F files=@assets/style.css \
+  -F files=@assets/js/app.js
+```
+
+The `filepaths` field is a JSON array where each element corresponds to the `files` field in order. The server uses these paths instead of the multipart filename.
+
 ### Site instance
 
 The returned object contains the deployment result plus convenience methods:
@@ -329,6 +350,34 @@ The returned object contains the deployment result plus convenience methods:
 | `redeploy(directory)` | directory path (string) | Upload new files, replacing all existing files. Returns a Promise. |
 | `delete(purge?)` | purge (boolean) | Delete the site. `false` = soft delete (files kept), `true` = purge S3 files. Returns a Promise. |
 
+### mygensite.manage(options)
+
+Create a management handle for an existing service when you already have the `slug` and `admin_token` (e.g. saved from a previous deploy). **Do not redeploy just to get a management object** — use this instead.
+
+```js
+const mygensite = require('mygensite');
+
+const site = mygensite.manage({
+  slug: 'demo',
+  admin_token: 'tok_xxx',       // from the original deploy/tunnel response
+  host: 'https://mygen.site',   // optional
+});
+
+// Same methods as deploy result
+await site.updateAccess({ mode: 'public' });
+await site.extendTTL(86400);
+await site.redeploy('./dist-v2');
+await site.delete();
+```
+
+#### Options
+
+| option | type | required | default | description |
+| --- | --- | --- | --- | --- |
+| `slug` | string | yes | — | The service slug |
+| `admin_token` | string | yes | — | The admin token from the original deploy/tunnel response |
+| `host` | string | | `https://mygen.site` | Server URL |
+
 ### Deploy management examples
 
 ```js

package/README.ko.md

@@ -301,11 +301,32 @@ const site = await mygensite.deploy({
   access: 'public',
   files: [
     { name: 'index.html', content: '<h1>Hello World</h1>' },
-    { name: 'style.css', content: 'body { font-family: sans-serif; }' },
+    { name: 'assets/style.css', content: 'body { font-family: sans-serif; }' },
   ],
 });
 ```
 
+#### curl로 배포
+
+Multipart의 `filename`은 디렉토리 경로를 제거합니다 (예: `assets/style.css` &rarr; `style.css`). 서브디렉토리가 있으면 `filepaths` JSON 필드를 사용하세요:
+
+```bash
+# 플랫 파일 (서브디렉토리 없음) - filepaths 불필요
+curl -X POST https://mygen.site/api/deploy \
+  -F slug=demo -F access='{"mode":"public"}' \
+  -F files=@index.html -F files=@style.css
+
+# 서브디렉토리 있음 - filepaths 필수
+curl -X POST https://mygen.site/api/deploy \
+  -F slug=demo -F access='{"mode":"public"}' \
+  -F 'filepaths=["index.html","assets/style.css","assets/js/app.js"]' \
+  -F files=@index.html \
+  -F files=@assets/style.css \
+  -F files=@assets/js/app.js
+```
+
+`filepaths`는 JSON 배열로, 각 원소가 `files` 필드와 순서대로 대응됩니다. 서버는 multipart filename 대신 이 경로를 사용합니다.
+
 ### Site 인스턴스
 
 반환 객체에 배포 결과와 편의 메서드가 포함됩니다:
@@ -329,6 +350,35 @@ const site = await mygensite.deploy({
 | `redeploy(directory)` | 디렉토리 경로 (string) | 새 파일로 교체 업로드. Promise 반환. |
 | `delete(purge?)` | purge (boolean) | 사이트 삭제. `false` = 소프트 삭제 (파일 유지), `true` = S3 파일까지 삭제. Promise 반환. |
 
+### mygensite.manage(options)
+
+기존 서비스의 `slug`과 `admin_token`이 있을 때 관리 핸들을 생성합니다 (예: 이전 배포에서 저장해둔 값).
+**관리 객체를 얻기 위해 재배포하지 마세요** — 이 함수를 사용하세요.
+
+```js
+const mygensite = require('mygensite');
+
+const site = mygensite.manage({
+  slug: 'demo',
+  admin_token: 'tok_xxx',       // 원래 배포/터널 생성 시 반환된 값
+  host: 'https://mygen.site',   // 선택
+});
+
+// deploy 결과와 동일한 메서드 사용 가능
+await site.updateAccess({ mode: 'public' });
+await site.extendTTL(86400);
+await site.redeploy('./dist-v2');
+await site.delete();
+```
+
+#### 옵션
+
+| 옵션 | 타입 | 필수 | 기본값 | 설명 |
+| --- | --- | --- | --- | --- |
+| `slug` | string | 예 | — | 서비스 slug |
+| `admin_token` | string | 예 | — | 원래 배포/터널 생성 시 반환된 admin token |
+| `host` | string | | `https://mygen.site` | 서버 URL |
+
 ### 배포 관리 예제
 
 ```js

package/README.md

@@ -66,6 +66,27 @@ await site.delete();                // soft delete
 await site.delete(true);            // purge (delete S3 files too)
 ```
 
+## Manage (existing service)
+
+Use `manage()` when you already have the `slug` and `admin_token` from a previous deploy or tunnel.
+**Do not redeploy just to get a management object** — use this instead.
+
+```js
+const mygensite = require('mygensite');
+
+const site = mygensite.manage({
+  slug: 'demo',
+  admin_token: 'tok_xxx',       // from the original deploy response
+  host: 'https://mygen.site',   // optional
+});
+
+// Same methods as deploy result
+await site.updateAccess({ mode: 'public' });
+await site.extendTTL(86400);
+await site.redeploy('./dist-v2');
+await site.delete();
+```
+
 ## Access Modes
 
 | mode | behavior |
@@ -147,6 +168,25 @@ mygensite deploy -d ./dist -s private-demo --access password --password 'mypass'
 mygensite deploy -d ./dist-v2 -s demo --admin-token tok_xxx
 ```
 
+## curl Deploy
+
+```bash
+# Simple (flat files)
+curl -X POST https://mygen.site/api/deploy \
+  -F slug=demo -F access='{"mode":"public"}' \
+  -F files=@index.html -F files=@style.css
+
+# With subdirectories — use filepaths to preserve directory structure
+curl -X POST https://mygen.site/api/deploy \
+  -F slug=demo -F access='{"mode":"public"}' \
+  -F 'filepaths=["index.html","assets/style.css","assets/js/app.js"]' \
+  -F files=@index.html \
+  -F files=@assets/style.css \
+  -F files=@assets/js/app.js
+```
+
+> **Note:** Multipart `filename` strips directory paths. The `filepaths` JSON field tells the server the correct path for each file, in order.
+
 ## Passwords with Special Characters
 
 When using the CLI or curl, passwords with special characters (like `!`, `$`, `&`, `\`) may be modified by your shell before reaching the program.

package/lib/deploy.js

@@ -170,9 +170,12 @@ async function deploy(options) {
   }
   form.append('access', JSON.stringify(accessObj));
 
+  // Send file paths as separate JSON field (busboy strips directories from filename)
+  form.append('filepaths', JSON.stringify(fileList.map(f => f.name)));
+
   for (const file of fileList) {
     form.append('files', file.content, {
-      filename: file.name,
+      filepath: file.name,
       contentType: file.contentType,
     });
   }
@@ -202,4 +205,36 @@ async function deploy(options) {
   return data;
 }
 
+/**
+ * Create a management handle for an existing service.
+ * Use this when you already have the slug and admin_token (e.g. from a previous deploy).
+ *
+ * @param {object} options
+ * @param {string} options.slug - The service slug
+ * @param {string} options.admin_token - The admin token from the original deploy
+ * @param {string} [options.host] - API host (default: https://mygen.site)
+ * @returns {object} Management object with updateAccess, extendTTL, redeploy, delete methods
+ */
+function manage(options) {
+  const {
+    slug,
+    admin_token,
+    host = DEFAULT_HOST,
+  } = options;
+
+  if (!slug) throw new Error('slug is required');
+  if (!admin_token) throw new Error('admin_token is required');
+
+  return {
+    slug,
+    admin_token,
+    url: `https://${slug}.${host.replace(/^https?:\/\//, '')}`,
+    updateAccess: (access) => patchService(host, slug, admin_token, { access }),
+    extendTTL: (ttl) => patchService(host, slug, admin_token, { ttl }),
+    redeploy: (dir) => deploy({ host, subdomain: slug, directory: dir, admin_token }),
+    delete: (purge) => deleteService(host, slug, admin_token, purge),
+  };
+}
+
 module.exports = deploy;
+module.exports.manage = manage;

package/localtunnel.js

@@ -16,6 +16,7 @@ function localtunnel(arg1, arg2, arg3) {
 }
 
 localtunnel.deploy = deploy;
+localtunnel.manage = deploy.manage;
 localtunnel.validate = validate;
 
 module.exports = localtunnel;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "mygensite",
   "description": "Expose your localhost to mygen.site with access control",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "license": "MIT",
   "repository": {
     "type": "git",