Vercel Project Configuration
Relevant source files
The following files were used as context for generating this wiki page:
The Vercel Project Configuration for the inkweave-admin repository defines the deployment environment and security protocols for the private administrative tools of the Inkweave ecosystem. This configuration ensures that administrative functionality remains isolated from the public application while sharing the core codebase via specific repository structures.
The system deploys a private instance of the application that integrates the public inkweave repository as a dependency. Security is maintained by enforcing Vercel-native authentication, ensuring only authorized team members access the admin interface.
Sources: README.md:1-5
Deployment Architecture
The deployment architecture utilizes a wrapper repository approach. The inkweave-admin repository acts as the host for administrative tools and configuration, while the main application logic is pulled in through a Git submodule.
Submodule Integration
The project pins the public application repository at a specific path. This allows the admin tools to build upon the existing codebase without duplicating the source code.
- Submodule Path:
upstream/inkweave - Source Repository:
Doberjohn/inkweave
Sources: README.md:3-4, .gitmodules
Environment Flow
The following diagram illustrates how the admin repository interacts with the upstream source and the Vercel deployment target.
The diagram shows the relationship between the admin repository, its upstream submodule, and the secured Vercel deployment environment.
Sources: README.md:3-5
Access Control and Security
The project implements a "Private Admin" model. Unlike the public application, this deployment is not accessible to general users.
Vercel Authentication
Access is restricted using Vercel's built-in authentication layer. The project configuration mandates a Vercel login to view any part of the deployed admin tools. This serves as the primary firewall against unauthorized access to administrative functions.
Sources: README.md:5, vercel.json
Project Governance
Operational rules and planning for the project are defined in local documentation files which guide the development and deployment process.
| Document | Purpose |
|---|---|
docs/PLAN.md | Contains the design, planning, and phase status for the admin tools. |
CLAUDE.md | Defines the working rules for the development environment. |
Sources: README.md:7-8, docs/PLAN.md, CLAUDE.md
Build and Configuration Details
The deployment process follows a standard Vercel pipeline but with specific requirements for submodule resolution.
- Repository Sync: Vercel clones
inkweave-admin. - Submodule Initialization: The build process fetches the content of
upstream/inkweave. - Authentication Binding: Vercel applies the "Vercel Login" protection to the generated deployment URL.
Sources: README.md:3-5, vercel.json
Summary
The Vercel Project Configuration for inkweave-admin establishes a secure, private environment for administrative tasks. By pinning the public inkweave repository as a submodule and enforcing Vercel-native login protections, the system maintains a clear boundary between public application logic and private administrative control.