what is mount-point?

[amitu]

In the context of fastn.app.

[amitu]

Regular dependencies in fastn.dependecy only provide elements that can be used from existing page. fastn.app can be used if a dependency wants to provide "urls".

When such fastn.app is used, it can be "installed" once or more on your fastn powered site. Each time you have to specify a "mount-point", which is the URL sub path on this the app is installed.

Say someone has created a reusable todo app, someone.com/todo-app, and it exposes a bunch of URLs someone.com/todo-app/ (the index page), someone.com/todo-app/settings/, someone.com/todo-app/add-todo/, someone.com/update-app/ etc. Say you are trying to install it on amitu.com. You can use mount-point to map amitu.com/ URLs to someone.com/todo-app.

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

-- fastn.app: someone.com/todo-app
mount-point: /my-todos/

So we have mounted someone.com/todo-app to amitu.com/my-todos/. Any request coming to amitu.com/my-todos/* will be served by someone.com/todo-app/*. So if someone accesses amitu.com/my-todos/settings, they will be actually accessing someone.com/todo-app/settings/ (or in other words, someone.com/todo-app/settings.ftd or someone.com/todo-app/settings/index.ftd will be invoked.

Note that the same app can also be mounted multiple times:

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

-- fastn.app: someone.com/todo-app
mount-point: /my-todos/

-- fastn.app: someone.com/todo-app
mount-point: /work-todos/

Now we have two "installs" of someone.com/todo-app, and each can be configured uniquely (checkout settings and capabilities to learn about how to configure an app).