You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
From a policy point of view I'm still of two minds as to whether we should do a premium mode, but I think it is worth developing a framework to support it.
Add a column to the user table for premium status. Certain features will check this column and if not true, will not display.
The quick and dirty way to modify premium status would be just to update that user's row in the DB. Alternately we could create an admin UI which would be able to modify user settings - that would be a separate feature though. This issue assumes that we're going to run an update user for each premium user.
And if we decided to start with a premium mode and then later make these features free for all, we could implement this change very quickly by updating all users to premium status.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From a policy point of view I'm still of two minds as to whether we should do a premium mode, but I think it is worth developing a framework to support it.
Add a column to the user table for premium status. Certain features will check this column and if not true, will not display.
The quick and dirty way to modify premium status would be just to update that user's row in the DB. Alternately we could create an admin UI which would be able to modify user settings - that would be a separate feature though. This issue assumes that we're going to run an update user for each premium user.
And if we decided to start with a premium mode and then later make these features free for all, we could implement this change very quickly by updating all users to premium status.
The text was updated successfully, but these errors were encountered: