mem8 1.2.0__tar.gz

mem8-1.2.0/.github/workflows/release.yml

@@ -0,0 +1,63 @@
+name: Semantic Release
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    concurrency: release
+    environment:
+      name: pypi
+      url: https://pypi.org/project/ai-mem/
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}  # pragma: allowlist secret
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Install dependencies
+        run: |
+          npm install -g semantic-release @semantic-release/git @semantic-release/exec @semantic-release/github
+
+      - name: Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          # Configure git
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+          # Run semantic-release
+          npx semantic-release
+
+      - name: Publish to PyPI
+        if: success()
+        env:
+          PYPI_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
+        run: |
+          # Check if dist directory exists (created by semantic-release)
+          if [ -d "dist" ]; then
+            echo "Publishing to PyPI..."
+            uv publish --token $PYPI_TOKEN
+          else
+            echo "No dist directory found, skipping PyPI publish"
+          fi

mem8-1.2.0/.gitignore

@@ -0,0 +1,25 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Output directory for generated templates
+out/
+out-*/
+test-*/
+*-files.txt
+
+.claude
+
+*.db
+
+.env
+.env.*local*
+.env.*.local*
+

mem8-1.2.0/.python-version

@@ -0,0 +1 @@
+3.12

mem8-1.2.0/.releaserc.json

@@ -0,0 +1,21 @@
+{
+  "branches": ["main"],
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    [
+      "@semantic-release/exec",
+      {
+        "prepareCmd": "sed -i 's/version = \".*\"/version = \"${nextRelease.version}\"/' pyproject.toml && echo '__version__ = \"${nextRelease.version}\"' > ai_mem/__init__.py && uv build"
+      }
+    ],
+    [
+      "@semantic-release/git",
+      {
+        "assets": ["pyproject.toml", "ai_mem/__init__.py"],
+        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+      }
+    ],
+    "@semantic-release/github"
+  ]
+}

mem8-1.2.0/CLAUDE.md

@@ -0,0 +1 @@
+- Use conventional commits as this project uses github actions that auto-pubish .github\workflows\release.yml

mem8-1.2.0/DOCKER.md

@@ -0,0 +1,150 @@
+# AI-Mem Docker Setup
+
+This document describes how to run AI-Mem using Docker for local development and production deployment.
+
+## Quick Start
+
+### Development Setup (Recommended)
+
+For local development with hot reload and easier debugging:
+
+```bash
+# Start database services only
+./scripts/dev-setup.sh
+
+# Then run backend and frontend locally
+cd backend && uv run python -m uvicorn aimem_api.main:app --reload --host 127.0.0.1 --port 8000
+cd frontend && npm run dev
+```
+
+### Full Stack Deployment
+
+For production-like deployment with all services in containers:
+
+```bash
+./scripts/deploy.sh
+```
+
+## Architecture
+
+### Services
+
+- **PostgreSQL**: Primary database (production-ready)
+- **Redis**: Cache and session storage
+- **Backend**: FastAPI application with automatic database migration
+- **Frontend**: Next.js application with optimized production build
+
+### Networking
+
+All services run on a dedicated Docker network (`aimem-network`) for secure inter-service communication.
+
+### Volumes
+
+- `postgres_data`: Persistent PostgreSQL data
+- `redis_data`: Persistent Redis data
+
+## Configuration
+
+### Environment Variables
+
+The backend uses these key environment variables:
+
+```env
+DATABASE_URL=postgresql+asyncpg://user:password@host:port/database
+REDIS_URL=redis://host:port
+SECRET_KEY=your-secret-key-minimum-32-characters
+DEBUG=false
+```
+
+### Development vs Production
+
+| Environment | Database | Redis | Frontend | Backend |
+|-------------|----------|-------|----------|---------|
+| Development | postgres-dev:5433 | redis-dev:6380 | Local (npm) | Local (uv) |
+| Production | postgres:5432 | redis:6379 | Container | Container |
+
+## Commands
+
+### Development
+
+```bash
+# Start infrastructure only
+docker-compose -f docker-compose.dev.yml up -d
+
+# View logs
+docker-compose -f docker-compose.dev.yml logs -f
+
+# Stop infrastructure
+docker-compose -f docker-compose.dev.yml down
+
+# Clean up volumes
+docker-compose -f docker-compose.dev.yml down -v
+```
+
+### Production
+
+```bash
+# Start all services
+docker-compose up -d
+
+# Build and start (rebuild images)
+docker-compose up --build -d
+
+# View logs
+docker-compose logs -f [service_name]
+
+# Stop all services
+docker-compose down
+
+# Clean up everything including data
+docker-compose down -v
+```
+
+## Health Checks
+
+All services include health checks:
+
+- **PostgreSQL**: `pg_isready` command
+- **Redis**: `redis-cli ping` command  
+- **Backend**: HTTP GET to `/api/v1/health`
+- **Frontend**: HTTP GET to root path
+
+## Troubleshooting
+
+### Database Connection Issues
+
+1. Ensure PostgreSQL is running: `docker-compose ps postgres`
+2. Check logs: `docker-compose logs postgres`
+3. Test connection: `docker-compose exec postgres psql -U aimem_user -d aimem`
+
+### Backend Startup Issues
+
+1. Check database connectivity
+2. Verify environment variables: `docker-compose exec backend env | grep DATABASE_URL`
+3. View backend logs: `docker-compose logs backend`
+
+### Port Conflicts
+
+If you get port binding errors:
+
+- Development: Uses ports 5433 (PostgreSQL), 6380 (Redis)
+- Production: Uses ports 5432 (PostgreSQL), 6379 (Redis), 8000 (Backend), 3000 (Frontend)
+
+Stop conflicting services or change ports in docker-compose files.
+
+## Orchestr8 Integration
+
+This Docker setup is designed to be cloud-native and compatible with Orchestr8 deployment:
+
+- All configuration via environment variables
+- Health checks for Kubernetes liveness/readiness probes
+- Multi-stage Dockerfiles for optimized production images
+- Proper volume mounts for persistent data
+- Network isolation for security
+
+To deploy with Orchestr8:
+
+1. Push images to your container registry
+2. Update `docker-compose.yml` with your image tags
+3. Configure environment variables for your cloud environment
+4. Use Orchestr8 to deploy the compose file to Kubernetes

mem8-1.2.0/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(which shall not include communications that are clearly marked or
+otherwise designated in writing by the copyright owner as "Not a Work").
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based upon (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and derivative works thereof.
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been submitted to Licensor.
+For the purposes of this definition, "Contribution" shall mean any
+work of authorship, including the original version of the Work and any
+modifications or additions to that Work or Derivative Works thereof,
+that is intentionally submitted to Licensor for inclusion in the Work
+by the copyright owner or by an individual or Legal Entity authorized
+to submit on behalf of the copyright owner. For the purposes of this
+definition, "submitted" means any form of electronic, verbal, or
+written communication sent to the Licensor or its representatives,
+including but not limited to communication on electronic mailing
+lists, source code control systems, and issue tracking systems that
+are managed by, or on behalf of, the Licensor for the purpose of
+discussing and improving the Work, but excluding communication that
+is conspicuously marked or otherwise designated in writing by the
+copyright owner as "Not a Contribution."
+
+"Contributor License Agreement" shall mean the agreement pursuant
+to which a Contributor grants the Licensor certain rights as defined
+below.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to use, reproduce, modify, display, perform,
+sublicense, and distribute the Work and such Derivative Works in
+Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, trademark, patent, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright notice and license terms to Your use,
+reproduction, and distribution of the Work or Derivative Works
+thereof, provided that the terms of such license are not inconsistent
+with the License and that You add a statement identifying such license
+as a separate license from this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Support. You may choose to offer, and to
+charge a fee for, warranty, support, indemnity or other liability
+obligations and/or rights consistent with this License. However, in
+accepting such obligations, You may act only on Your own behalf and on
+Your sole responsibility, not on behalf of any other Contributor, and
+only if You agree to indemnify, defend, and hold each Contributor
+harmless for any liability incurred by, or claims asserted against,
+such Contributor by reason of your accepting any such warranty or support.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!)  The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same page as the copyright notice for easier identification within
+third-party archives.
+
+Copyright 2024 AI-Mem Contributors
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.