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
People periodically request a way to manage data in a cocalc project using a database, e.g., postgresql, sqlite, etc.
Maybe we should add that. This issue is a place to collect thoughts.
One fun idea - there is an open source webapp discussed here https://news.ycombinator.com/item?id=42320032 that would provide a nice web based way to work with a database that is deployed in a project. Installing this and configuring it by default to point at a database would be nice. Unfortunately that is AGPL, so we would have to be extremely careful about the blast radius involved in using it. But we could maybe write something similar, or look at alternatives.
Other relevant things:
For cocalc dev we have a little python script that deploys postgresql locally and works very well. This is something that could save people hours of work.
It may also make sense to deploy a database standalone on a compute server, since then you can use a LOT of disk space efficiently, though you have to worry some about network usage and latency. But making it easy and ensuring it uses the wireguard vpn we have (for secure communication between any two nodes) would be valuable. Also, we obviously need to add the cocalc home base to the vpn (not done yet).
The text was updated successfully, but these errors were encountered:
People periodically request a way to manage data in a cocalc project using a database, e.g., postgresql, sqlite, etc.
Maybe we should add that. This issue is a place to collect thoughts.
One fun idea - there is an open source webapp discussed here https://news.ycombinator.com/item?id=42320032 that would provide a nice web based way to work with a database that is deployed in a project. Installing this and configuring it by default to point at a database would be nice. Unfortunately that is AGPL, so we would have to be extremely careful about the blast radius involved in using it. But we could maybe write something similar, or look at alternatives.
Other relevant things:
The text was updated successfully, but these errors were encountered: