ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Scalingo implements zero-downtime deployments through rolling updates, where new containers are spun up and health-checked before the previous version is terminated. This mechanism ensures continuous traffic flow via the platform's load balancer. When deploying Java applications using Hibernate ORM, there is a potential conflict between the rolling update pr
Database Schema Transition Ory Kratos manages identity data using a SQL database, where schema updates are applied via the ory migrate sql command during version transitions. While the identity attributes are stored in a flexible JSONB format in PostgreSQL, the underlying table structures are subject to version-specific migrations. Migration Constraints Curr
PM2's zero-downtime reload mechanism sequentially restarts process instances in cluster mode to maintain application availability. While this ensures the service remains online, it creates a period where multiple versions of the application code coexist during the transition. When a deployment includes a destructive database schema change, the remaining acti
When migrating data from an external PostgreSQL instance to a Supabase project using the postgres_fdw extension, the transfer of table rows does not automatically synchronize the state of sequence generators. In a zero-downtime migration strategy, data is pulled into the target Supabase instance while the source continues to accept writes. If the target sequ
The goal is to revert database schema changes applied during a module upgrade on Yunohost v2.0.0. The core relies on Symfony/Doctrine migrations, yet no generic rollback command is exposed to undo all module‑specific changes in one step. Current constraints include a manual backup dump that must be restored to recover from a failed migration, which is non‑at
Moving a small application from a development workspace to a hosted Replit Deployment requires a transition from a shared workspace environment to a production-ready target, such as a Reserved VM. While the platform manages traffic routing to ensure zero-downtime via health checks, the handling of persistent data during this switch remains a design concern.
In a Symfony application using Doctrine Migrations, I am planning a release that includes a destructive schema change (dropping a column that existing code still reads). I want a rollback plan I can actually trust, but the more I look at how migrations work, the less clear the safe path is. My understanding is that doctrine:migrations:migrate with a target v
Transitioning from Legacy Query API to select() SQLAlchemy 2.0 introduces a significant architectural shift by removing the legacy Session.query() method in favor of the Core-style select() construct. While the 1.4 series provided a compatibility shim via the future=True flag on create_engine , this transition boundary is absolute in version 2.0. The primary
ory
pm2
supabase
yunohost
replit
symfony
python
sqlalchemy
hibernate
scalingo