Pre-release

@erichanson erichanson released this Jul 13, 2018 · 57 commits to master since this release

Assets 2

Ho! Now comes Aquameta v0.2.0 release candidate 2. Lots of new features to talk about:

  • bundle remotes have been completely refactored to use postgres_fdw instead of http. This makes the process of cloning, pushing and pulling between instances of Aquameta much simpler. A new user interface is taking shape called the "bundle manager", which enables pushing and cloning between connected databases.
  • bundles can now be exported to csv file with the bundle.bundle_export_csv() function. All parts of a bundle are saved to file, and then can be imported via bundle.bundle_import_csv().
  • major strides in making Aquameta secure out of the box, most noteworthy of which is that anonymous is no longer a superuser. Instead a limited set of row-level permissions are granted to the anonymous user, allowing them to only do what is needed to register, confirm and login, or at least that's the idea.
  • There is an alternate uwsgi config file that enables SSL encryption via letsencrypt. Users should be able to just follow the letsencrypt instructions, run certbot and create an SSL certificate.
  • The endpoint.resource* tables now have an active flag instead of a unique constraint on resource.path, so that multiple resources that use the same path can be activated and deactivated instead of just breaking their checkout.
  • Documentation! There's now a quickstart and cheatsheet in the docs/ folder.
  • The very simple email facilities in endpoint for sending registration emails etc., have been moved into an email extension. It has a configurable smtp_server table that can contain multiple SMTP configurations. It works very nicely with an Amazon SES instance, or any other SMTP server that supports DKIM, so emails don't get sent to the spam folder. It also has the start of a simple email template system.
  • Now each core modules has it's own associated bundle, which contains rows specific to that module:
    • org.aquameta.core.bundle
    • org.aquameta.core.docs
    • org.aquameta.core.event
    • org.aquameta.core.filesystem
    • org.aquameta.core.http_client
    • org.aquameta.core.ide
    • org.aquameta.core.meta
    • org.aquameta.core.p2p
    • org.aquameta.core.semantics
    • org.aquameta.core.widget
    • org.aquameta.core.www
  • Lots of user interface bundles in early stages:
    • org.aquameta.ui.admin - Generic data editing admin, with mixin widgets for building apps
    • org.aquameta.ui.auth - Register, login and auth status widgets for general use or extension
    • org.aquameta.ui.dev - Main development UI, still very primitive
    • org.aquameta.ui.fsm - UI state fsm
    • org.aquameta.ui.layout - Tabs, modals, select panes, etc.
    • org.aquameta.ui.tags - HTML tag wrappers for sync'ing datums into tags
  • Lots of bug fixes
  • Instructions for installing on Amazon EC2
Pre-release

@erichanson erichanson released this Aug 31, 2017 · 155 commits to master since this release

Assets 2

Hi all,

I'm happy to announce the release of Aquameta, a peer-to-peer network for exchanging "bundles", a new kind of complex data object that can be almost anything. They can include code, web apps, data, images and more, and together create a kind of "smart object" that is very versatile and open-ended.

Today, users can exchange emails, publish web pages, exchange binaries via p2p apps, and much more. We'd like to see Aquameta become another kind of communication protocol and network, one where users exchange these bundled complex data objects that hopefully do fun, interesting and useful stuff. Because bundles are made up of data, we claim that it's a very wide pipe for creativity and interactivity, one that opens up a world of new possibilities.

Under the hood, Aquameta is a bunch of PostgreSQL schemas that handle things like version control, web hosting, user interface, events, peer to peer communication, etc. A bundle is made up of rows in these tables and any others that users might wish to create.

Aquameta has a web interface that lets users build and exchange these bundles. They can be sent either server-to-server via http, or browser-to-browser via WebRTC. The networked-communication aspect of Aquameta is still under development and experimentation.

Aquameta can be installed on a desktop, a server, in the cloud or on a small device such as a Raspberry Pi.

Under the hood are a lot of PostgreSQL modules which hopefully can be useful to the PostgreSQL community. They include:

  1. meta - a writable system catalog, that makes common DDL operations like schema changes accessible via INSERT, UPDATE and DELETE
insert into meta.role(name, superuser, password) values ('joe', true, 'mypass');
insert into meta.schema(name) values ('my_schema');
  1. bundle - a version control system for data, similar to git, but for rows in the database instead of files
select bundle.stage_row_add(
    meta.row_id('public','countries','id','UK')
);
select bundle.commit('org.aquameta.countries','add uk.');
select bundle.checkout('org.aquameta.games.snake');
  1. event - a pub/sub event system for subscribing to data changes on a particular column, row or table
select session_create();
select subscribe_table(meta.relation_id('widget','machine'));
  1. filesystem - a foreign data wrapper that lets you SELECT files and directories from the filesystem, and a daemon called postgrefs, which lets you navigate the database from the filesystem as if it were files and directories
aquameta=# select name, path, permissions, content, owner from filesystem.file where path='/etc/issue';
 name  |    path    | permissions |         content          | owner 
-------+------------+-------------+--------------------------+-------
 issue | /etc/issue | 0644        | Ubuntu 14.04.5 LTS \n \l+| root
       |            |             |                         +| 
       |            |             |                          | 
(1 row)
$ ls /mnt/aquameta/public/countries
  1. www - a web server that exposes the database over http, including a REST interface for data manip and function calls, hosting of arbitrary resources, and an authentication layer that uses PostgreSQL ROLEs and PRIVILEGEs
aquameta=# select path, m.mimetype, substring(content from 1 for 15) 
from endpoint.resource r 
join endpoint.mimetype m on r.mimetype_id = m.id limit 2;
 path  | mimetype  |    substring    
-------+-----------+-----------------
 /docs | text/html | <!DOCTYPE html>
 /dev  | text/html | <!DOCTYPE html>
select endpoint.request('0.1','GET','/docs')
  1. widget - a user interface component framework, where web pages are composed of "widgets", UI components made of html, css and javascript, that accept arguments and support javascript dependencies
select * from widget.widget;
select * from widget.widget_dependency_js;
  1. semantics - a metadata layer for the database schema, where columns, relations, foreign keys and more can be "decorated" with additional semantic meaning
insert into semantics.relation (relation_id, purpose_id, widget_id) values
(
   meta.relation_id('ecomm','customer'),
   (select purpose_id from semantics.purpose where purpose='row_detail'),
   (select id from widget.widget where name='customer_list_view')
);

Aquameta is in very early stages, despite being under development for years. It is finally at the point of being a marginally functional prototype that hopefully is pointed in the right direction, but there is much work still to be done. The user interface is just beginning to take shape, the system is not secure, test coverage is sparse, and there are surely many bugs and missing features. We are releasing it at this early stage to get feedback and invite contributors to help out.

To give Aquameta a spin, head over to github and consult the README which contains install instructions:

http://github.com/aquametalabs/aquameta

To jump into development, check out the project's roadmap, and join our IRC channel and mailing list:

http://aquameta.org/roadmap
#aquameta on irc.freenode.net
https://groups.google.com/forum/#!aboutgroup/aquameta-discuss