mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Install aide

Install AIDE, prepare your computer once, sign in, create a project and open its secure web address.

Beta
OverviewInstallWorkflowsOperateCustomizeInsideProblems and fixesAll components
Steps

Six steps from a Linux host to a project URL.

Installing AIDE, preparing the host and creating a cluster are separate steps, and success at one does not prove the next. You need Linux of the Debian or Ubuntu family with Docker, sudo and a local DNS forwarder that reads /etc/aidcx/dns/aide-servers.conf; the requirements list the rest.

  1. Illustrative
    Install through aidc
    aidc login
aidc install mait:aide@latest
    Step 1 of 6

    Install AIDE with AIDC

    AIDE is installed through AIDC. The product install needs usable MAIT credentials, so sign in to AIDC first.

    What you get

    An aide executable on your path, installed by a tool you can inspect with aidc list mait.

  2. Capturedaide 0.7.4
    Check the executable
    $ aide version
    aide 0.7.4
    Step 2 of 6

    Check that it runs

    aide version and aide help COMMAND are the forms to use; --help and --version are not accepted at the top level. A version answer shows the program runs. It does not show the host is ready.

    What you get

    The release you are running.

  3. Capturedaide 0.7.4
    Check the host
    $ aide setup --check
     
    Dependencies
     
    NAME VERSION SOURCE STATUS
    k3d 5.8.3 aidc missing
    kubectl 1.35.3 aidc missing
    helm 4.1.4 aidc missing
    dnsmasq latest apt installed
    privileged-setup n/a system installed
    Step 3 of 6

    Prepare the host once

    aide setup --check reports what is present and changes nothing. On a host that has not been prepared it lists what is missing and exits 1.

    aide setup installs k3d, kubectl, Helm and the dnsmasq package, and adds an administrator helper that cluster creation needs. It is safe to repeat. The helper can be run by your account without a password, so review it with your environment owner on a shared machine.

    What you get

    Every row of the dependency table reports installed.

  4. Illustrative
    Sign in and confirm access
    aide login
aide cluster list
    Step 4 of 6

    Sign in

    aide login prints an activation address and asks for the login code the page shows. aide cluster list needs no project file: it prints No clusters registered on a new machine, or an activation link when the cluster feature is not yet active. Open the link; signing in again does not add the feature.

    What you get

    Credentials that include the cluster feature, confirmed by a command that reads them.

  5. Illustrative
    Write the project file
    aide init --name myproject --domain dev.mycompany.io --ca-generate
[ok] Created .aide.yaml
  Project: myproject
  Domain: dev.mycompany.io
  CA: will be generated at cluster create
    Step 5 of 6

    Create a project

    For a cluster you will stop and start, keep your own CA with --ca-cert and --ca-key instead of --ca-generate; a generated CA is recreated on every start.

    What you get

    A .aide.yaml in the project directory, ready to commit.

  6. Illustrative
    Create and check
    aide cluster create
aide cluster status
getent hosts <hostname>
curl --fail --show-error https://<hostname>/
    Step 6 of 6

    Create the cluster and open its URL

    Create streams its progress, and its final message only waits briefly: it does not test your application. Deploy an application and an ingress route for a hostname under your domain, then run the last two commands yourself. The tutorial does this end to end.

    What you get

    A running cluster, a project CA your machine trusts, and an HTTPS response you checked.

Next

Where to go next.

  • Workflows, for live reload, stop and start, and the agent brief