A local development environment should disappear. You shouldn’t think about it until you need something, and then it should already be there. These are the nine things people tend to notice first about LampRabit.
1. Every folder is a website
Drop shop into www and open https://shop.test. No virtual-host files, no hosts-file editing, no restart dance. If the project has a public/ folder, that’s what’s served. Sub-domains (api.shop.test) work too.
2. HTTPS that your browser actually trusts
Click Trust certificate once. From then on every site, and every sub-domain, has a valid certificate, renewed automatically. Secure cookies, service workers and OAuth callbacks just work. (More on local HTTPS.)
3. A PHP version per project
Install PHP 8.1 to 8.5 side by side. The legacy WordPress site stays on 8.1, the new Laravel app runs 8.4, both at once. In a terminal inside a project, php and composer follow that project’s version too.
4. Your Node.js dev server, at a real address
Run npm run dev the way you always do, in LampRabit or your own terminal. LampRabit sees the port and points project.test at it in a few seconds; when you stop the server, the domain goes back to the files. Never type localhost:5173 again. (How it works.)
5. The whole stack, free
Apache and Nginx, MariaDB and MySQL, Redis and Memcached, Mailpit, phpMyAdmin, Adminer, phpRedisAdmin, Composer. Every runtime is a one-click download checked against its published checksum, and you can keep several versions. No paid tier hides the database.
6. Errors that explain themselves
When a service won’t start, LampRabit says why in plain language: port 80 is used by httpd.exe (XAMPP), the Visual C++ runtime is missing, line 42 of this config is invalid. Then it offers the fix. Health checks confirm a service is actually answering, not just running.
7. New projects that ask the right questions
Laravel, Symfony, WordPress, Drupal, Statamic, Magento, CakePHP, CodeIgniter, Next.js, Nuxt, Astro, Vite, Express, NestJS. Each template asks the same questions the framework’s own installer does, creates the database, writes .env, and leaves nothing behind if a step fails. You can write your own in YAML.
8. One place for every log
Apache, Nginx, PHP, MariaDB, Mailpit, each project’s dev server and the commands you ran, all searchable (regex too), filterable by severity and source, and exportable. The diagnostics report hides your user name before you paste it into a bug report.
9. Respect for your machine
LampRabit runs as your normal user and asks for administrator rights only for the hosts file and certificate trust. Quitting stops its services; nothing lingers holding a port. Uninstalling removes what it created and keeps your projects and databases.
Plus the small stuff: keyboard shortcuts for everything (? shows them), stack profiles (“Laravel”, “WordPress”) that start just the services you need, one-click public URLs for sharing, light and dark themes, and signed automatic updates.
See how this compares to other tools in Why LampRabit is different, or download it free.
