Choosing Your Project Setup

Introduction: Choosing Your Project Setup

Before you create a project in Wappler, two choices shape your first experience:

1. Development Environment: where the project runs while you build it.
2. Server Model: what backend technology powers dynamic features.

For a beginner, this is not about choosing the perfect long-term architecture. It is about choosing a setup that lets you learn quickly without extra friction.

Development Environment

Choose where the project runs while you build, test, and preview it.

Server Model

Choose the backend engine that powers dynamic features and later tutorials.

Development Environment

This choice controls where your project runs during development.

Think of it as your local workspace for testing pages, server actions, and data.

Common choices:

• Wappler Local Server: the easiest starting point, with the least setup.
• Own Server: use this if you already work with tools like WAMP, XAMPP, or IIS.
• Docker: useful when you want a more production-like environment, but it adds concepts to learn.

If your main goal is to learn Wappler first, choose the option that removes the most setup work.

Wappler Local Server

The easiest starting point for learning because setup stays minimal.

Own Server

Useful if you already work with WAMP, XAMPP, IIS, or another established local stack.

Docker

Closer to production-style environments, but it introduces more moving parts to learn.

Server Model

This choice defines what backend technology your project can use for dynamic features.

Common choices:

• NodeJS: recommended for most new users and the smoothest default path in current Wappler onboarding.
• PHP: a good fit if your stack or hosting already depends on PHP.
• ASP.NET: use this when your app is built around the Microsoft .NET ecosystem.
• None: for static HTML-only projects with no server-side logic.

You are not being asked to master these technologies here. You are only choosing the engine that will power later dynamic steps.

NodeJS

Best default for new users and the smoothest match for current onboarding.

PHP

A solid choice when your hosting or existing stack already depends on PHP.

ASP.NET

Fits projects that live inside the Microsoft .NET ecosystem.

None

Use this only for static HTML projects with no server-side logic.

Conclusion: Recommended Starter Setup

If you are new to Wappler, start with:

• Development Environment: Wappler Local Server
• Server Model: NodeJS

That combination keeps the setup simple and matches the main onboarding path.

You can always add more environments later, but your first goal is to create one project successfully and keep moving.

Recommended combo

Wappler Local Server plus NodeJS keeps your first project simple and aligned with the main learning path.

Why it works

You remove extra setup overhead now, then explore more environments later once the basics feel familiar.