Apppublic

isayan58/Professional_Digital_Twin

sourceHugging Faceupdated 17d agoView on Hugging Face

1likes

App README

Your Professional Digital Twin

This Space runs a published image. Nothing here is a copy of the source, so updates arrive without you re-creating the Space, and your keys stay yours.

Set up, once

1. A database. Any managed PostgreSQL with the pgvector extension; the free tiers at Neon and Supabase are enough. Spaces have no durable disk, so the database has to live outside this container.

2. Settings → Variables and secrets:

Key	Kind	Value
`DATABASE_URL`	secret	Your database URL, with the `postgresql+psycopg://` prefix
`ANTHROPIC_API_KEY`	secret	Your Anthropic key
`AUTH_SECRET`	secret	Any random string, 32+ characters
`SHARE_TOKEN_SECRET`	secret	A different random string, 32+ characters
`APP_ENV`	variable	`production`

Set APP_ENV=production together with those two secrets, never before them and never without them: the guard that refuses placeholder secrets only runs in production, so leaving it unset silently ships a public deployment on the shipped default key.

3. Open the Space and create your account. Signup closes after the first one.

Staying up to date

The Dockerfile tracks :latest, so each release reaches you on the next factory rebuild (Settings → Factory rebuild). A plain restart is not enough: it reuses the image already built and never checks for a newer one.

To have that happen on its own, add:

Key	Kind	Value
`SELF_UPDATE_ENABLED`	variable	`true`
`SELF_UPDATE_SPACE_ID`	variable	`your-username/your-space`
`HF_TOKEN`	secret	A Hugging Face token with write access to your Space

That token stays in your Space and is used only to rebuild your own deployment.

To pin a version instead, replace :latest in the Dockerfile with a release tag. Nothing will change until you edit that line.