Update Postiz service template from v2.10.1 to v2.21.9 #10854
CagriKIRT
started this conversation in
Improvement Requests
Replies: 1 comment
|
This is my current .yml file for v2.22.1: (it has temporal and it's postgres + elasticsearch) services:
postiz:
image: 'ghcr.io/gitroomhq/postiz-app:v2.22.1'
environment:
- SERVICE_URL_POSTIZ_5000
- 'MAIN_URL=${SERVICE_URL_POSTIZ}'
- 'FRONTEND_URL=${SERVICE_URL_POSTIZ}'
- 'NEXT_PUBLIC_BACKEND_URL=${SERVICE_URL_POSTIZ}/api'
- 'JWT_SECRET=${SERVICE_PASSWORD_JWTSECRET}'
- 'DATABASE_URL=postgresql://postgres:${SERVICE_PASSWORD_POSTGRESQL}@postgres:5432/${POSTGRESQL_DATABASE:-postiz-db}'
- 'REDIS_URL=redis://default:${SERVICE_PASSWORD_REDIS}@redis:6379'
- 'BACKEND_INTERNAL_URL=http://localhost:3000'
- 'TEMPORAL_ADDRESS=temporal:7233'
- 'RUN_CRON=${RUN_CRON:-true}'
- 'DISABLE_REGISTRATION=${DISABLE_REGISTRATION:-false}'
- 'API_LIMIT=${API_LIMIT:-30}'
- 'CLOUDFLARE_ACCOUNT_ID=${CLOUDFLARE_ACCOUNT_ID}'
- 'CLOUDFLARE_ACCESS_KEY=${CLOUDFLARE_ACCESS_KEY}'
- 'CLOUDFLARE_SECRET_ACCESS_KEY=${CLOUDFLARE_SECRET_ACCESS_KEY}'
- 'CLOUDFLARE_BUCKETNAME=${CLOUDFLARE_BUCKETNAME}'
- 'CLOUDFLARE_BUCKET_URL=${CLOUDFLARE_BUCKET_URL}'
- 'CLOUDFLARE_REGION=${CLOUDFLARE_REGION}'
- 'STORAGE_PROVIDER=${STORAGE_PROVIDER:-local}'
- 'UPLOAD_DIRECTORY=${UPLOAD_DIRECTORY:-/uploads}'
- 'NEXT_PUBLIC_UPLOAD_DIRECTORY=${NEXT_PUBLIC_UPLOAD_DIRECTORY:-/uploads}'
- 'NEXT_PUBLIC_UPLOAD_STATIC_DIRECTORY=${NEXT_PUBLIC_UPLOAD_STATIC_DIRECTORY}'
- 'RESEND_API_KEY=${RESEND_API_KEY}'
- 'EMAIL_FROM_ADDRESS=${EMAIL_FROM_ADDRESS}'
- 'EMAIL_FROM_NAME=${EMAIL_FROM_NAME}'
- 'EMAIL_PROVIDER=${EMAIL_PROVIDER}'
- 'X_URL=${X_URL}'
- 'X_API_KEY=${SERVICE_X_API}'
- 'X_API_SECRET=${SERVICE_X_SECRET}'
- 'LINKEDIN_CLIENT_ID=${SERVICE_LINKEDIN_ID}'
- 'LINKEDIN_CLIENT_SECRET=${SERVICE_LINKEDIN_SECRET}'
- 'REDDIT_CLIENT_ID=${SERVICE_REDDIT_API}'
- 'REDDIT_CLIENT_SECRET=${SERVICE_REDDIT_SECRET}'
- 'GITHUB_CLIENT_ID=${SERVICE_GITHUB_ID}'
- 'GITHUB_CLIENT_SECRET=${SERVICE_GITHUB_SECRET}'
- 'THREADS_APP_ID=${SERVICE_THREADS_ID}'
- 'THREADS_APP_SECRET=${SERVICE_THREADS_SECRET}'
- 'FACEBOOK_APP_ID=${SERVICE_FACEBOOK_ID}'
- 'FACEBOOK_APP_SECRET=${SERVICE_FACEBOOK_SECRET}'
- 'YOUTUBE_CLIENT_ID=${SERVICE_YOUTUBE_ID}'
- 'YOUTUBE_CLIENT_SECRET=${SERVICE_YOUTUBE_SECRET}'
- 'TIKTOK_CLIENT_ID=${SERVICE_TIKTOK_ID}'
- 'TIKTOK_CLIENT_SECRET=${SERVICE_TIKTOK_SECRET}'
- 'PINTEREST_CLIENT_ID=${SERVICE_PINTEREST_ID}'
- 'PINTEREST_CLIENT_SECRET=${SERVICE_PINTEREST_SECRET}'
- 'DRIBBBLE_CLIENT_ID=${SERVICE_DRIBBLE_ID}'
- 'DRIBBBLE_CLIENT_SECRET=${SERVICE_DRIBBLE_SECRET}'
- 'TUMBLR_CLIENT_ID=${SERVICE_TUMBLR_ID}'
- 'TUMBLR_CLIENT_SECRET=${SERVICE_TUMBLR_SECRET}'
- 'DISCORD_CLIENT_ID=${SERVICE_DISCORD_ID}'
- 'DISCORD_CLIENT_SECRET=${SERVICE_DISCORD_SECRET}'
- 'DISCORD_BOT_TOKEN_ID=${SERVICE_DISCORD_TOKEN}'
- 'SLACK_ID=${SERVICE_SLACK_ID}'
- 'SLACK_SECRET=${SERVICE_SLACK_SECRET}'
- 'SLACK_SIGNING_SECRET=${SLACK_SIGNING_SECRET}'
- 'MASTODON_URL=${MASTODON_URL:-https://mastodon.social}'
- 'MASTODON_CLIENT_ID=${SERVICE_MASTODON_ID}'
- 'MASTODON_CLIENT_SECRET=${SERVICE_MASTODON_SECRET}'
- 'INSTAGRAM_APP_ID=${INSTAGRAM_APP_ID}'
- 'INSTAGRAM_APP_SECRET=${INSTAGRAM_APP_SECRET}'
- 'BEEHIIVE_API_KEY=${SERVICE_BEEHIIVE_KEY}'
- 'BEEHIIVE_PUBLICATION_ID=${SERVICE_BEEHIIVE_PUBID}'
- 'OPENAI_API_KEY=${SERVICE_OPENAI_KEY}'
- 'NEXT_PUBLIC_DISCORD_SUPPORT=${NEXT_PUBLIC_DISCORD_SUPPORT}'
- 'NEXT_PUBLIC_POLOTNO=${NEXT_PUBLIC_POLOTNO}'
- IS_GENERAL=true
- 'NX_ADD_PLUGINS=${NX_ADD_PLUGINS:-false}'
- 'NOT_SECURED=${NOT_SECURED:-false}'
- 'FEE_AMOUNT=${FEE_AMOUNT:-0.05}'
- 'STRIPE_PUBLISHABLE_KEY=${STRIPE_PUBLISHABLE_KEY}'
- 'STRIPE_SECRET_KEY=${STRIPE_SECRET_KEY}'
- 'STRIPE_SIGNING_KEY=${STRIPE_SIGNING_KEY}'
- 'STRIPE_SIGNING_KEY_CONNECT=${STRIPE_SIGNING_KEY_CONNECT}'
volumes:
- 'postiz_config:/config/'
- 'postiz_uploads:/uploads/'
depends_on:
postgres:
condition: service_healthy
redis:
condition: service_healthy
temporal:
condition: service_healthy
healthcheck:
test:
- CMD
- node
- '-e'
- "const r=require('http').get('http://localhost:5000/',res=>process.exit(res.statusCode<500?0:1));r.on('error',()=>process.exit(1));r.setTimeout(4000,()=>{r.destroy();process.exit(1)})"
interval: 30s
timeout: 10s
retries: 5
start_period: 120s
postgres:
image: 'postgres:14.5'
volumes:
- 'postiz_postgresql_data:/var/lib/postgresql/data'
environment:
- POSTGRES_USER=postgres
- 'POSTGRES_PASSWORD=${SERVICE_PASSWORD_POSTGRESQL}'
- 'POSTGRES_DB=${POSTGRESQL_DATABASE:-postiz-db}'
healthcheck:
test:
- CMD-SHELL
- 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB:-postiz-db}'
interval: 5s
timeout: 20s
retries: 10
redis:
image: 'redis:7.2'
environment:
- 'REDIS_PASSWORD=${SERVICE_PASSWORD_REDIS}'
command: 'redis-server --requirepass ${SERVICE_PASSWORD_REDIS}'
volumes:
- 'postiz_redis_data:/data'
healthcheck:
test:
- CMD
- redis-cli
- '-a'
- '${SERVICE_PASSWORD_REDIS}'
- ping
interval: 5s
timeout: 10s
retries: 20
temporal-elasticsearch:
image: 'elasticsearch:7.17.27'
environment:
- cluster.routing.allocation.disk.threshold_enabled=true
- cluster.routing.allocation.disk.watermark.low=512mb
- cluster.routing.allocation.disk.watermark.high=256mb
- cluster.routing.allocation.disk.watermark.flood_stage=128mb
- discovery.type=single-node
- 'ES_JAVA_OPTS=-Xms256m -Xmx256m'
- xpack.security.enabled=false
volumes:
- 'temporal_elasticsearch_data:/usr/share/elasticsearch/data'
expose:
- 9200
healthcheck:
test:
- CMD-SHELL
- 'curl -fsS "http://localhost:9200/_cluster/health?wait_for_status=yellow&timeout=5s" || exit 1'
interval: 10s
timeout: 10s
retries: 10
start_period: 60s
temporal-postgresql:
image: 'postgres:16'
environment:
- POSTGRES_USER=temporal
- POSTGRES_PASSWORD=temporal
volumes:
- 'temporal_postgresql_data:/var/lib/postgresql/data'
expose:
- 5432
healthcheck:
test:
- CMD-SHELL
- 'pg_isready -U temporal'
interval: 10s
timeout: 5s
retries: 5
start_period: 10s
temporal:
image: 'temporalio/auto-setup:1.28.1'
depends_on:
temporal-postgresql:
condition: service_healthy
temporal-elasticsearch:
condition: service_healthy
environment:
- DB=postgres12
- DB_PORT=5432
- POSTGRES_USER=temporal
- POSTGRES_PWD=temporal
- POSTGRES_SEEDS=temporal-postgresql
- DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development-sql.yaml
- ENABLE_ES=true
- ES_SEEDS=temporal-elasticsearch
- ES_VERSION=v7
- TEMPORAL_NAMESPACE=default
configs:
-
source: temporal-dynamicconfig
target: /etc/temporal/config/dynamicconfig/development-sql.yaml
expose:
- 7233
healthcheck:
test:
- CMD
- temporal
- operator
- cluster
- health
- '--address'
- 'temporal:7233'
interval: 10s
timeout: 5s
retries: 10
start_period: 30s
configs:
temporal-dynamicconfig:
content: "limit.maxIDLength:\n - value: 255\n constraints: {}\nsystem.forceSearchAttributesCacheRefreshOnRead:\n - value: true # Dev setup only. Please don't turn this on in production.\n constraints: {}\n"
volumes:
postiz_config: null
postiz_uploads: null
postiz_postgresql_data: null
postiz_redis_data: null
temporal_postgresql_data: null
temporal_elasticsearch_data: null |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
[Enhancement]: Postiz service template outdated — v2.10.1 → v2.21.9
The Postiz one-click service in Coolify uses an outdated image:
The latest release is v2.21.9 (https://github.com/gitroomhq/postiz-app/releases/tag/v2.21.9), which is many versions ahead.
What needs to be updated
v2.10.1tov2.21.9Impact
Users deploying Postiz via Coolify's one-click service are stuck on a very old version missing many features and bug fixes. A manual update is possible but an official template refresh would help everyone.
All reactions