Alternatives to Local by Flywheel logo

Alternatives to Local by Flywheel

MAMP, XAMPP, Bitnami, Docker, and Vagrant are the most popular alternatives and competitors to Local by Flywheel.
33
66
+ 1
3

What is Local by Flywheel and what are its top alternatives?

It is a free local development environment designed to simplify the workflow of WordPress developers and designers. It makes creating a local WordPress site a light breeze. Any site created with it, will automatically have a self-signed certificate created.
Local by Flywheel is a tool in the CMS Tools category of a tech stack.

Top Alternatives to Local by Flywheel

  • MAMP

    MAMP

    It can be installed under macOS and Windows with just a few clicks. It provides them with all the tools they need to run WordPress on their desktop PC for testing or development purposes, for example. It doesn't matter if you prefer Apache or Nginx or if you want to work with PHP, Python, Perl or Ruby. ...

  • XAMPP

    XAMPP

    It consists mainly of the Apache HTTP Server, MariaDB database, and interpreters for scripts written in the PHP and Perl programming languages. ...

  • Bitnami

    Bitnami

    Our library provides trusted virtual machines for every major development stack and open source server application, ready to run in your infrastructure. ...

  • Docker

    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • Vagrant

    Vagrant

    Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux. ...

  • Elementor

    Elementor

    Create beautiful websites using a simple, intuitive drag and drop Interface.It offers pixel perfect design, yet produces 100% clean code. Take your design vision and turn it into a stunning custom-made website. It's fast and easy. ...

  • WP Rocket

    WP Rocket

    Speed up your WordPress website, more trafic, conversions and money with this caching plugin. Caching creates an ultra-fast load time, essential for improving Search Engine Optimization and increasing conversions. ...

  • SwiftLint

    SwiftLint

    It is a tool to enforce Swift style and conventions, loosely based on GitHub's Swift Style Guide.It hooks into Clang and SourceKit to use the AST representation of your source files for more accurate results. ...

Local by Flywheel alternatives & related posts

MAMP logo

MAMP

50
106
2
A free, local server environment
50
106
+ 1
2
PROS OF MAMP
  • 1
    Comes with PHP and phpmyadmin preinstalled
  • 1
    Great Support of Native Languages
CONS OF MAMP
    Be the first to leave a con

    related MAMP posts

    Helfried Plenk
    Senior Partner at IBS IT-DL GmbH · | 1 upvote · 94.4K views
    Shared insights
    on
    MAMPMAMPXAMPPXAMPPJoomla!Joomla!

    installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

    See more
    XAMPP logo

    XAMPP

    97
    201
    6
    A free and open-source cross-platform web server solution stack package
    97
    201
    + 1
    6
    PROS OF XAMPP
    • 6
      Easy set up and installation of files
    CONS OF XAMPP
      Be the first to leave a con

      related XAMPP posts

      Helfried Plenk
      Senior Partner at IBS IT-DL GmbH · | 1 upvote · 94.4K views
      Shared insights
      on
      MAMPMAMPXAMPPXAMPPJoomla!Joomla!

      installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

      See more
      Bitnami logo

      Bitnami

      118
      160
      6
      The App Store for Server Software
      118
      160
      + 1
      6
      PROS OF BITNAMI
      • 6
        Cloud Management
      CONS OF BITNAMI
        Be the first to leave a con

        related Bitnami posts

        Docker logo

        Docker

        115.7K
        94.9K
        3.8K
        Enterprise Container Platform for High-Velocity Innovation.
        115.7K
        94.9K
        + 1
        3.8K
        PROS OF DOCKER
        • 821
          Rapid integration and build up
        • 688
          Isolation
        • 517
          Open source
        • 505
          Testa­bil­i­ty and re­pro­ducibil­i­ty
        • 459
          Lightweight
        • 217
          Standardization
        • 182
          Scalable
        • 105
          Upgrading / down­grad­ing / ap­pli­ca­tion versions
        • 86
          Security
        • 84
          Private paas environments
        • 33
          Portability
        • 25
          Limit resource usage
        • 15
          I love the way docker has changed virtualization
        • 15
          Game changer
        • 12
          Fast
        • 11
          Concurrency
        • 7
          Docker's Compose tools
        • 4
          Because its fun
        • 4
          Easy setup
        • 4
          Fast and Portable
        • 3
          Makes shipping to production very simple
        • 2
          It's dope
        • 1
          Very easy to setup integrate and build
        • 1
          Does a nice job hogging memory
        • 1
          Package the environment with the application
        • 1
          Open source and highly configurable
        • 1
          Simplicity, isolation, resource effective
        • 1
          Highly useful
        • 1
          MacOS support FAKE
        • 1
          Its cool
        • 1
          Docker hub for the FTW
        • 1
          HIgh Throughput
        CONS OF DOCKER
        • 7
          New versions == broken features
        • 5
          Unreliable networking
        • 5
          Documentation not always in sync
        • 3
          Moves quickly
        • 2
          Not Secure

        related Docker posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.5M views

        Our whole DevOps stack consists of the following tools:

        • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
        • Respectively Git as revision control system
        • SourceTree as Git GUI
        • Visual Studio Code as IDE
        • CircleCI for continuous integration (automatize development process)
        • Prettier / TSLint / ESLint as code linter
        • SonarQube as quality gate
        • Docker as container management (incl. Docker Compose for multi-container application management)
        • VirtualBox for operating system simulation tests
        • Kubernetes as cluster management for docker containers
        • Heroku for deploying in test environments
        • nginx as web server (preferably used as facade server in production environment)
        • SSLMate (using OpenSSL) for certificate management
        • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
        • PostgreSQL as preferred database system
        • Redis as preferred in-memory database/store (great for caching)

        The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

        • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
        • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
        • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
        • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
        • Scalability: All-in-one framework for distributed systems.
        • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
        See more
        Tymoteusz Paul
        Devops guy at X20X Development LTD · | 23 upvotes · 4.8M views

        Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

        It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

        I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

        We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

        If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

        The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

        Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

        See more
        Vagrant logo

        Vagrant

        8.5K
        6.3K
        1.5K
        A tool for building and distributing development environments
        8.5K
        6.3K
        + 1
        1.5K
        PROS OF VAGRANT
        • 352
          Development environments
        • 291
          Simple bootstraping
        • 238
          Free
        • 139
          Boxes
        • 132
          Provisioning
        • 84
          Portable
        • 81
          Synced folders
        • 69
          Reproducible
        • 51
          Ssh
        • 44
          Very flexible
        • 5
          Works well, can be replicated easily with other devs
        • 5
          Easy-to-share, easy-to-version dev configuration
        • 3
          Great
        • 2
          Quick way to get running
        • 2
          Just works
        • 1
          What is vagrant?
        • 1
          Container Friendly
        • 1
          DRY - "Do Not Repeat Yourself"
        • 1
          Good documentation
        CONS OF VAGRANT
        • 2
          Can become v complex w prod. provisioner (Salt, etc.)
        • 2
          Multiple VMs quickly eat up disk space
        • 1
          Development environment that kills your battery

        related Vagrant posts

        Tymoteusz Paul
        Devops guy at X20X Development LTD · | 23 upvotes · 4.8M views

        Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

        It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

        I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

        We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

        If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

        The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

        Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

        See more
        Tim Abbott
        Shared insights
        on
        VirtualBoxVirtualBoxVagrantVagrantZulipZulip
        at

        We use VirtualBox primarily as a Vagrant provider for macOS for the Zulip development environment. It's totally reasonable software for providing a convenient virtual machine setup on macOS (and for debugging when things go wrong, which is mostly how we use it since the Vagrant provider for macOS just works).

        See more
        Elementor logo

        Elementor

        1.4K
        103
        0
        Drag & Drop page builder for WordPress
        1.4K
        103
        + 1
        0
        PROS OF ELEMENTOR
          Be the first to leave a pro
          CONS OF ELEMENTOR
            Be the first to leave a con

            related Elementor posts

            WP Rocket  logo

            WP Rocket

            485
            21
            0
            Premium Caching Plugin for WordPress
            485
            21
            + 1
            0
            PROS OF WP ROCKET
              Be the first to leave a pro
              CONS OF WP ROCKET
                Be the first to leave a con

                related WP Rocket posts

                SwiftLint logo

                SwiftLint

                76
                70
                0
                A tool to enforce Swift style and conventions
                76
                70
                + 1
                0
                PROS OF SWIFTLINT
                  Be the first to leave a pro
                  CONS OF SWIFTLINT
                    Be the first to leave a con

                    related SwiftLint posts