Deploy an application. The whole thing.

From a Git repository to the services your users rely on: the deployment workflow designed for NodalX.

All guides

Start with the complete project

An application is more than an image or a web page. It may combine a frontend, API, database, files, cache and background jobs. Deploying the code alone does not make the whole system usable.

NodalX treats the project as the unit of work. From a Git repository or supported import, it identifies services, dependencies, ports and persistence needs. It prepares a plan and asks for missing access, secrets or decisions.

Prepare a deployment

  • Connect an authorized repository or inspect an existing application import.
  • Review detected services, their resources and required access.
  • Choose the environment and placement policy, then approve the plan.

The deployment action starts builds, placement, startup, checks and routing according to that plan. Automation connects these steps; missing information and risky migrations still require a decision.

Test without changing production

A test environment brings together the web app, API and test data in an isolated copy. Its secrets stay separate. External actions such as email or payments need to be neutralized or configured for testing.

You can validate a new version in use before releasing it. Promoting a version does not mean copying test data into the production database.

Go live and keep a record

NodalX prepares and checks instances, then progressively sends them traffic according to the release policy. The commit, artifacts and configuration remain linked to the deployed version. Domains, HTTPS certificates and routes are part of the same workflow.

Rolling code back does not turn back time in a database. Migration and write compatibility need to be assessed before switching. Returning to an older version is different from restoring data.