Development accounts

.gitignore

@@ -5,3 +5,7 @@ node_modules
 *.vsix
 .vscode-test-web/
 .vscode/settings.json
+output.html
+mindmap.html
+/webapp/mindmap.html
+/webapp/.env

.gitlab-ci.yml

@@ -0,0 +1,47 @@
+# .gitlab-ci.yml - Placed in the ROOT directory
+
+image: node:18 # Use a Node.js image compatible with your project (Node 18+ needed for fetch in convert.js)
+
+stages:
+  - deploy
+
+deploy_webapp:
+  stage: deploy
+  # Optional: Only run on changes to the main branch or specific directories
+  # rules:
+  #   - if: '$CI_COMMIT_BRANCH == "main" || $CI_COMMIT_BRANCH == "master"'
+  #     changes:
+  #       - webapp/**/* # Trigger only if webapp files change
+  #       - .gitlab-ci.yml
+  script:
+    - echo "Deploying webapp..."
+    - cd webapp # Navigate into the webapp directory
+    - echo "Current directory: $(pwd)"
+    - echo "Listing files: $(ls -la)"
+    - echo "Node version: $(node -v)"
+    - echo "NPM version: $(npm -v)"
+    - echo "Installing dependencies using npm ci..."
+    - npm ci # Use 'ci' for faster, deterministic installs based on package-lock.json
+    - echo "Dependencies installed."
+    # --- Deployment Action ---
+    # The following command STARTS the server, but it will only run for the duration of the CI job.
+    # For persistent deployment, you need a runner configured to host Node.js apps
+    # (e.g., using pm2, Docker on a server, Kubernetes, etc.)
+    # Option 1: Run directly (for testing CI step, NOT persistent)
+    # - node server.js
+    # Option 2: Use PM2 (if installed on your runner/server)
+    # - npm install -g pm2 # Or ensure pm2 is pre-installed
+    # - pm2 start server.js --name mindmap-webapp --update-env # Starts or restarts the app
+    # Option 3: Build & Push Docker image (Requires Dockerfile and GitLab Container Registry setup)
+    # See Dockerfile example below. Uncomment and adapt if using Docker.
+    # - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
+    # - docker build -t $CI_REGISTRY_IMAGE:latest .
+    # - docker push $CI_REGISTRY_IMAGE:latest
+    # --- Choose ONE deployment strategy appropriate for your runner/hosting ---
+    - echo "Build complete. Runner needs to handle persistent execution."
+    - echo "To run manually: cd webapp && node server.js"
+    - npm install -g pm2 # Or ensure it's pre-installed on the runner machine
+    - pm2 restart server.js --name mindmap-webapp || pm2 start server.js --name mindmap-webapp
+  environment:
+    name: production # Optional: Define environment
+    # url: http://your-deployment-url.com # Optional: Link to deployed app

README.md

@@ -1,40 +0,0 @@
-# markmap-vscode
-
-[![vscode](https://img.shields.io/visual-studio-marketplace/v/gera2ld.markmap-vscode)](https://marketplace.visualstudio.com/items?itemName=gera2ld.markmap-vscode)
-[![open vsx](https://img.shields.io/open-vsx/v/gera2ld/markmap-vscode)](https://open-vsx.org/extension/gera2ld/markmap-vscode)
-
-This extension integrates [markmap](https://markmap.js.org/) into VSCode.
-
-## Features
-
-- Preview markdown files as markmap
-- Edit markdown files in a text editor and the markmap will update on the fly
-- Works offline
-
-<img width="1014" alt="markmap" src="https://user-images.githubusercontent.com/3139113/97068999-5f9e8480-15ff-11eb-8222-43d26cecade5.png">
-
-## Usage
-
-### Command Palette
-
-Open a markdown file. Then open the Command Palette (⇧⌘P) and search `Open as markmap`, press enter.
-
-### Context menu
-
-Right click on a markdown file, then choose `Open as markmap`.
-
-### Button on title-bar
-
-Open a markdown file. Find the markmap icon on the editor title-bar and click it.
-
-![title button](https://user-images.githubusercontent.com/3139113/110966366-25f0cf00-8390-11eb-9a16-3c4d66712f47.png)
-
-## Configuration
-
-### Custom CSS
-
-Extra CSS to customize the style of markmap.
-
-### Default Options
-
-Default options for Markmap, see <https://markmap.js.org/docs/json-options#markmap-for-vscode> for more details.