MaleusMaleus

Connect git and configure deployment targets

Wire your project to a git remote, then add the deployment targets, hosted by Maleus or on your own infrastructure, you want to promote versions to.

In the appProject settings
On this page

Two settings sections work together to make a version shippable: Git Repository (where the code lives) and Deployments (where each version goes). You configure them once at the start of the project.

Connect a git remote

This step is a prerequisite for everything related to deployments.

  1. Open the project, then Settings.
  2. In the sidebar's Settings drill, pick Git Repository.
  3. The page shows one of four states.
    • Loading while we resolve the current configuration.
    • Empty if no remote is configured. Use the form to connect one.
    • Configure form to enter the remote URL and credentials.
    • Configured once it's wired up. The remote URL is shown along with a push action.
  4. Save. Maleus can now push commits to the remote.

Without a configured remote, the Deployments section is locked. There's nowhere for promoted versions to go.

Add deployment targets

A deployment target is where a version goes when you promote it. When you create one, the Hosting field offers two modes.

ModeWhat happensWhen to pick it
Internal deploymentMaleus hosts and manages the environment. The target is a staging or a production, with its branch and the URLs it serves.The most common case, recommended by default.
External deploymentMaleus pushes the version to a branch of your repository, then your own pipeline takes over, on your infrastructure.When IT keeps control of hosting and the deployment pipeline.

An internal target is an environment, a branch and the URL it serves.

  1. Still in the Settings drill, pick Deployments, then Add deployment.
  2. Pick the Hosting.
    • Internal deployment: choose the environment (staging or production) and the branch, then fill in the served URLs if needed.
    • External deployment: give it any name (for example "Client CI") and the branch your pipeline watches.
  3. Save, then repeat for every environment you want to ship to.

A project has at most one internal staging and one production target, and as many external targets as it needs. Each one shows up as its own column on the Versions page when you promote.

Creating and editing deployment targets is admin-only. The deployment type cannot be changed after creation.

External deployment: business teams ship on their own

Once an admin has set up the external target, an application's owner promotes each new version to it from the versions list, exactly like staging, without going through the infrastructure team. Your pipeline triggers on the branch and deploys under your own rules.

  • Your teams can write to the branch too. If someone pushed a commit in the meantime (a hotfix, for example), Maleus replays the version on top instead of overwriting it. There is never a force push.
  • The branch must share the project's history. If it has no commit in common with the project, the promotion stops and a message asks you to check the branch configured on the target.

On an internal target, the branch belongs to Maleus: a promotion that finds commits pushed by someone else is refused, and the branch is left untouched.

Once that's done

  • Mark a version as Done to move it into the Ready to Deploy column.
  • Promote it to any target from the versions list. See Promote a version.

Other settings worth a look

While you're in Settings, two more sections are worth knowing about.

SectionWhat it does
EnvironmentsStatus of the dev sandbox, agent sandboxes, and workshop sandboxes. Restart from here if something stalls.
Maleus SDKSnippet to install the tracing widget. Feeds the App Reviews page.

Danger zone

The General section has a Delete this project action at the bottom. Destructive and not reversible.