Overview of Nimbella projects, actions, and deployment
Projects are deployed as a unit into your Nimbella Cloud namespace to make them visible to your end-users to the extent that you wish. Any number of projects may deploy into a namespace, and a project may deploy into different namespaces at different times. An application can have any number of projects to achieve its full functionality. This modular approach also lets you share projects across apps.
On the other hand,
nim provides some special support for the model where namespaces are tied to specific projects, which have the sole right to deploy to them. It is possible to tie two namespaces to each project, one for testing, one for production. The support for this model is described in tieing namespaces to projects.
Projects can contain actions, or static web content, or both (e.g. the front-end and backend of an application). Each action, and the web content, may optionally have build steps. The following sections show you how to go from simple to complex:
- Example: Create and deploy a project with a single action
- Add static web content to a project
- Add build steps to a project
Projects can be deployed without any configuration, but in more complex cases you can add a project configuration.