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
I realized the above works well for those who have admin access, like @yolile. But maybe you want also access for others?
I also think that you have one PostgreSQL container per dengue chat? So it is not a shared instance with multiple projects? In this case what we could do is deploy a locked-down instance of phppgadmin which is configured to connect only to that container. We could even make it using our nginx reverse proxy so that it is available under https://<denguechat domain>/phppgadmin or something. So that it is clear that it is instance for that particular deployment of denguechat.
Then it i on you to coordinate how you distribute access to the database. You can even make non-admin users on the database with read-only access and things like that.
Just sent out an email and I think we do need this. not only for DengueChat, but also for AppCivist I would say. It's frequently good to access and study dat directly in the DB.
Also, denguechat has a redis instance we would be good to have an access to at least create backups.
Just sent out an email and I think we do need this. not only for DengueChat, but also for AppCivist I would say. It's frequently good to access and study dat directly in the DB.
Who should be accessing this? And how often? This is the main question here to see what is worth doing.
Also, denguechat has a redis instance we would be good to have an access to at least create backups.
For better management and checking of issues, we would need a way to access the database.
The text was updated successfully, but these errors were encountered: