Application Blocks
Application blocks are the main building bricks of your infrastructure. They represent your web applications, APIs, or frontends.
Available blocks
- Laravel — PHP application with the Laravel framework
- React — React frontend application
- Angular — Angular frontend application
- Vue.js — Vue.js frontend application
- Docker — Custom Docker container for any other framework or language
A configuration that reveals itself progressively
Application blocks perfectly illustrate Fransys's dynamic approach. Instead of immediately presenting all possible parameters, the interface enriches step by step as you configure your block.
Example: the Laravel block
Step 1 — The block has just been added. The interface displays only the essential parameters: the platform, the code source, and the port.

At this stage, the sidebar shows only two tabs: General configuration and Environment variables, plus Metrics and Logs. No noise, no unnecessary fields.
Step 2 — You connect your Git provider. New fields appear: the choice between GitLab, GitHub, or External, and the invitation to connect your account.

Step 3 — You select a repository. Once your Git account is connected, the interface reveals the repository and branch selectors, as well as the Connect CI button.

Step 4 — CI configures itself automatically. Fransys generates a complete CI/CD pipeline for your project. The interface guides you through 4 clear steps:

- Create the merge request — Fransys automatically creates an MR containing the CI configuration
- Follow the instructions — Open and review the merge request
- Merge — Integrate the CI into your branch
- Verify — Once the pipeline succeeds, your latest commit appears in Fransys
You don't have to write any CI file manually — Fransys handles it entirely.
Example: the Docker block
The same principle applies to the Docker block.
Initially, the block displays only the basic parameters: the source (GitLab, GitHub, or External), the Docker image, and the port. The sidebar contains only General configuration, Metrics, and Logs.

As soon as you provide a Docker image, the interface enriches: new tabs appear in the sidebar — Recurring, Resources, Storage, Environment variables, Deployment commands — and new sections like Ingress (with the auto-generated URL *.fransysapp.com) and Egress appear in the general configuration.

This dynamic behavior applies to all Fransys blocks. The interface only shows you what's relevant at each moment. If a tab or field doesn't appear, it's because it's not yet necessary — configure the basic elements and the rest will follow.