Your first project

This page walks you through the minimum configuration needed to get a deployable project in fDeploy. It assumes you already have:

• fDeploy Server running and reachable (see installation)
• fDeploy Agent installed on at least one Windows machine you want to deploy to (see agent installation)
• An administrator account to sign in with

By the end you will have one environment, one registered deployment target, one progression, and a project with a single deployment step — everything the next page needs to run a deployment.

1. Create an environment

Navigate to Infrastructure → Environments and create an environment. A short name is fine for now — Dev is a common choice.

You only need one environment to complete this walkthrough. In real use you would normally have several (Dev, Test, Staging, Production, …) — see environments for how scoping works.

2. Register your deployment target

Navigate to Infrastructure → Deployment targets and add the Windows machine you installed the agent on. You will need its hostname or IP address and the agent’s thumbprint (printed by the agent installer and available in the agent’s service log).

Assign the target to the environment you just created, and give it at least one role — web-server is a useful default if you plan to deploy an IIS site. Roles are what lets a deployment step select which targets it runs on; see target roles for the model.

Wait for the target’s status to go Healthy before continuing. An Unavailable target indicates a connectivity or thumbprint issue — see deployment targets for troubleshooting.

3. Create a progression

Navigate to Library → Progressions and create a progression. Give it one phase that maps to the environment you created.

Progressions enforce deployment gating across phases (Deployment gating) — with a single phase, there is nothing to gate, which is fine for a first project. In real use you add phases for each stage of your release pipeline.

4. Create the project

Navigate to Projects and create a new project. Give it a name, pick the progression you just created, and save.

5. Add a deployment step

Open the project, go to the Deployment process tab, and add one step. The simplest starter is Execute a script — a one-line PowerShell step that writes a message or touches a file on the target. Assign the step to the web-server role (or whichever role your target has).

If your real use case is deploying an IIS website, pick Deploy to IIS instead and fill in the site name, application pool, and binding — but be aware that IIS deployment requires a package to be uploaded first, which we cover in the next page.

See deployment steps for the full step reference.

6. (Optional) Define a variable

Open the Variables tab on the project and create a variable (e.g. Greeting with value Hello from fDeploy). If your PowerShell step references #{Variable.Greeting} in its script body, fDeploy will substitute the value at deploy time.

Variables become more interesting when scoped per environment — see variables.

You’re ready to deploy

At this point the project is deployable. Continue to Your first deployment to create a release and push it to your environment.