Spaces:
Paused
Paused
Commit History
-
change emoji to 📝 (notepad)
7ac2f89
-
docs: add HuggingFlow to More Projects section
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>83c8430
-
fix: correct typo in project name "HuggingMes" in README
751478a
-
refactor: remove cloudflare-worker.js and related configurations
010e97a -
refactor: replace UptimeRobot with Cloudflare Workers for service keep-alive mechanism
5d2b465 -
chore: update X OAuth instructions, increase default SYNC_INTERVAL, and adjust app navigation paths
2869840 -
update
bb56821
-
fix: set FRONTEND_URL to bare origin so CORS allow-origin matches browser
FRONTEND_URL was set to PUBLIC_URL/app (with basePath suffix). Postiz backend uses FRONTEND_URL as the CORS allowed-origin. Browsers send Origin: https://host (scheme+host only, no path per the HTTP spec), so the /app suffix caused every pre-flight and credentialed request to be blocked — making login and signup silently fail. Fix: FRONTEND_URL = PUBLIC_URL (no /app). Email links generated by Postiz (e.g. ${FRONTEND_URL}/auth/login) still work because health-server now redirects any bare /auth/* path to /app/auth/*. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>ff3303a
-
fix: move next build to container startup — HF builder cgroup too small
next build for Postiz needs ~4 GB RSS. The HF Space builder has a ~4 GB cgroup limit, making it impossible to complete in docker build regardless of heap tuning, single-thread flags, or multi-stage tricks (exit 137). Solution: don't run next build in the Dockerfile at all. Run it in start.sh at container startup where the runtime has 16 GB RAM. Bonuses over the docker-build approach: - NEXT_PUBLIC_BACKEND_URL is baked with the real SPACE_HOST URL (correct) instead of localhost (broken) because we now know it at build time - First boot ~5-8 min; all subsequent boots restore .next from HF Dataset backup and skip the build entirely Changes: - Dockerfile: remove all frontend build steps; back to clean 2-stage; HEALTHCHECK start-period raised to 600s for first-boot window - start.sh: build frontend at startup if .next/BUILD_ID absent; 8 GB heap (runtime has 16 GB); shows progress in logs - postiz-sync.py: include .next (minus webpack cache) in backup tarball; restore on boot so…866a8e6 -
Fix OOM build (exit 137) by disabling sourcemap generation
Postiz upstream enables both Next.js productionBrowserSourceMaps and Sentry's webpack sourcemap plugin. Together they push peak build memory past HF Space builder limits (16 GB cap), causing OOMKilled at exit 137. Patch apps/frontend/next.config.js during build: - productionBrowserSourceMaps: true → false - Sentry sourcemaps.disable: false → true Also lower per-app heap from 4 GB to 3 GB and build the four Postiz apps sequentially (backend → workers → cron → frontend) instead of in parallel — concurrent Next.js + Nest builds each spawn worker pools and stack peak RSS. README updated for /app routing (Postiz UI mounted at /app/*, dashboard owns /, OAuth callback URLs need the /app prefix). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>8de0b02 -
initialize project
b4d7c1c