Skip to content

[v5.x] feat(cloud): user and team inactivity management#9873

Open
peaklabs-dev wants to merge 5 commits intonextfrom
v5.x-feat/inactivity-management
Open

[v5.x] feat(cloud): user and team inactivity management#9873
peaklabs-dev wants to merge 5 commits intonextfrom
v5.x-feat/inactivity-management

Conversation

@peaklabs-dev
Copy link
Copy Markdown
Member

@peaklabs-dev peaklabs-dev commented Apr 29, 2026

I am overall not the biggest fan of inactivity tracking on services where the service sends you an email or deletes your account after 6 months of inactivity for example. So core Coolify will not have inactivity tracking in general.

However, as we are migrating all database data from v4 to v5 during the upgrade migration, for this one isolated case (the migration) it makes sense to not migrate over inactive users and teams. This will speed up migration, clean up the v5 databases and also save disk space.

Changes

  • Add ended_at column to subscriptions table
  • Set subscription ended_at on cancellations, expirations or refunds
  • Backfill ended_at for past subscriptions
  • Add inactive tracking to users and teams
  • Add mark inactive command

Note: This command is intended to only be run 30 days from the scheduled upgrade migration to v5 on the cloud version, not before


This is part 1 of 2 in a stack made with GitButler:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant