-
-
Notifications
You must be signed in to change notification settings - Fork 4k
Description
📜 Description
I am testing an image upload that is 4096x4096 in jpeg. It falls below X's 5MB Limit and at the max resolution that X delivers. The image uploads but is still capped at 1000x1000.
👟 Reproduction steps
Use the Disable_Image_Compression ENV tag at true.
👍 Expected behavior
When uploading this image its at full resolution on the docker image itself. When posting to X, it should be fairly painless and remain at the full resolution.

👎 Actual Behavior with Screenshots
This is the largest image that is posted by X at 1000x1000 even though it should be at 4096x4096 
💻 Operating system
Linux
🤖 Node Version
v20.18.1
📃 Provide any additional context for the Bug.
docker compose
services: postiz: image: ghcr.io/gitroomhq/postiz-app:latest container_name: postiz restart: always environment: # You must change these. Replace postiz.your-server.com` with your DNS name - this needs to be exactly the URL you're accessing Postiz on.
MAIN_URL: "http://localhost:5000"
FRONTEND_URL: "http://localhost:5000"
NEXT_PUBLIC_BACKEND_URL: "http://localhost:5000/api"
JWT_SECRET: "SECRET REMOVED"
# These defaults are probably fine, but if you change your user/password, update it in the
# postiz-postgres or postiz-redis services below.
DATABASE_URL: "postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-local"
REDIS_URL: "redis://postiz-redis:6379"
BACKEND_INTERNAL_URL: "http://localhost:3000"
IS_GENERAL: "true" # Required for self-hosting.
NOT_SECURED: "true"
DISABLE_REGISTRATION: "true"
env_file:
- .env
volumes:
- postiz-config:/config/
- postiz-uploads:/uploads/
ports:
- 5000:5000
networks:
- postiz-network
depends_on:
postiz-postgres:
condition: service_healthy
postiz-redis:
condition: service_healthy
postiz-postgres:
image: postgres:17-alpine
container_name: postiz-postgres
restart: always
environment:
POSTGRES_PASSWORD: postiz-password
POSTGRES_USER: postiz-user
POSTGRES_DB: postiz-db-local
volumes:
- postgres-volume:/var/lib/postgresql/data
networks:
- postiz-network
healthcheck:
test: pg_isready -U postiz-user -d postiz-db-local
interval: 10s
timeout: 3s
retries: 3
postiz-redis:
image: redis:7.2
container_name: postiz-redis
restart: always
healthcheck:
test: redis-cli ping
interval: 10s
timeout: 3s
retries: 3
volumes:
- postiz-redis-data:/data
networks:
- postiz-network
volumes:
postgres-volume:
external: false
postiz-redis-data:
external: false
postiz-config:
external: false
postiz-uploads:
external: false
networks:
postiz-network:
external: false
.env file# === Storage Settings
STORAGE_PROVIDER: "local"
UPLOAD_DIRECTORY: "/uploads"
NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"
DISABLE_IMAGE_COMPRESSION: "true"
#Twitter/X
X_API_KEY: "REMOVED"
X_API_SECRET: "REMOVED"
X_CLIENT: "REMOVED"
X_SECRET: "REMOVED"
#Meta
INSTAGRAM_APP_ID: "REMOVED"
INSTAGRAM_APP_SECRET: "REMOVED"
THREADS_APP_ID: "REMOVED"
THREADS_APP_SECRET: "REMOVED"
`
👀 Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
None