package, and capabilities / system

[amitu]

We have to relook how packages work, and how systems capabilities work etc for 0.5.

FASTN.ftd

We can simplify FASTN.ftd by ignore the -- import: fastn part, there was no real fastn module being imported, and we were dealing with FASTN.ftd file as if they valid fastn files. A bunch of fastn is not available to FASTN.ftd, and probably it does not make sense for us to make it fully executable file, and we treat it as a file with p1 syntax only.

-- package: foo
-- dependency: name-of-dependency

Get Rid Of Dependency Alias

We have both dependency alias feature, and auto import feature, and dependency feature can be easily emulated with auto import, and is auto import is overall superior. So we can remove dependency alias in 0.5.

Systems

We have discussed systems and capabilities in the past, but I am feeling like we can simplify it.

No Need For system: Key

Earlier to designate any package as system you have to use:

-- fastn.package: fastn-community.github.io/design-system
system: ds

I feel this is too much bureaucracy. For one you have to pick a globally unique system alias, and further you hope that the package you intend to "provide" / "overwrite", has declared itself as a system.

Now any package you add as a dependency, can be overwritten by the FASTN.ftd of the main package.

Global Provided-Via

-- import: fastn
-- fastn.package: amitu.com

-- fastn.dependency: fastn-community.github.io/design-system
provided-via: amitu.com/ds

-- fastn.dependency: fastn-community.github.io/doc-site

Here if any package in the dependency tree imported fastn-community.github.io/design-system, they will instead get amitu.com/ds. Same with submodules, eg fastn-community.github.io/design-system/foo will be amitu.com/ds/foo etc.

Sensitive Dependency

Some modules can be sensitive, and we do not want to allow to everyone.

-- package: amitu.com

-- dependency: fastn-community.github.io/design-system
provides-via: amitu.com/ds
sensitive: true

-- dependency: foo.com
-- dependency: fastn-community.github.io/doc-site
allow: amitu.com/ds

This is basically saying that fastn-community.github.io/design-system is a sensitive package, and since it is sensitive, it is not automatically available to every dependency, and fastn-community.github.io/doc-site can access amitu.com/ds, but not foo.com dependency (if foo.com has imported fastn-community.github.io/design-system, it will raise an error).

Different Modules With Same Capabilities

Say you have two databases, so you configure them:

-- package: amitu.com

-- dependency: fastn-community.github.io/db
provides-via: amitu.com/db-prod
sensitive: true

-- dependency: fastn-community.github.io/db
provides-via: amitu.com/db-dev
sensitive: true

-- dependency: foo.com
allow: amitu.com/db-dev

-- dependency: fastn-community.github.io/doc-site
allow: amitu.com/db-prod

Here you are allowing fastn-community.github.io/doc-site the prod db, and foo.com gets dev db only.

url-mappings, dynamic-urls, and redirects

In v0.4 we support:

-- fastn.redirects: 

/ftd/kernel/ -> /kernel/
/discord/ -> https://discord.gg/eNXVBMq4xt

-- fastn.url-mappings:

/-/auth/* -> wasm+proxy://email_auth.wasm/*
/ft2/* -> wasm+proxy://ft2.wasm/*

-- fastn.dynamic-urls:

# ide
url: /ide/<string:slug>/
document: ide/index.ftd

We can combine all of them under some urls section.