Devenv

What is devenv?

Imagine devenv to function as a dependency manager for the services and packages that you need to run your application for local development or even in a CI/CD context.

Similar to other package managers, devenv lets you describe what your environment should look like and locks dependencies to a specific version to help you compose a reproducible setup.

Devenv not only lets you choose from and install different versions of binaries (e.g., PHP, Node, npm), but it also allows you to configure and run services (like MySQL, Redis, OpenSearch). The binaries and states of the services are stored on a per-project level.

The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine.

Installation

Nix

As devenv is built on top of Nix, first install Nix with the following command based on your OS:

curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install

Using Oh My ZSH?

You probably won't be able to use the commands below. Use the following steps to continue using oh my zsh:

• Open /etc/zshrc and look for lines enclosed in # Nix and # End Nix like so (probably at the end of the file):

# Nix

# ... content ...

# End Nix

• Copy the lines block enclosed in # Nix and # End Nix
• Open ~/.zshrc and add the copied lines to the end of this file
• Initiate the terminal with source ~/.zshrc or reboot your terminal for nix to work
• Delete the lines between # Nix and # End Nix from /etc/zshrc

Credits: "nixos installation issue,'command not found: nix'", StackOverflow

Devenv

Finally, install/update devenv:

nix-env --install --attr devenv -f https://github.com/NixOS/nixpkgs/tarball/nixpkgs-unstable

You can find the whole installation guide for devenv in their official documentation:

Getting started - devenv.sh

Shopware

Depending on whether you want to set up a fresh Shopware project or contribute to the Shopware core, you have to choose between the Symfony Flex template or the Shopware project.

Since the environment is described via a devenv.nix file committed to version control, you can now boot up the environment:

devenv up

WARNING

Make sure that the ports for the services are not already in use, or else the command will fail.

Check your default web services with the following commands:

Change your .env file to the correct database settings:

# <PROJECT_ROOT>/.env
DATABASE_URL="mysql://shopware:shopware@127.0.0.1:3306/shopware?sslmode=disable&charset=utf8mb4"

Start a new terminal, navigate to the project directory and run the following command to launch a devenv shell. This shell includes all necessary programs (php, composer, npm, node, etc.) to initialize Shopware:

devenv shell

In the devenv shell, run the following command to initialize Shopware:

bin/console system:install --basic-setup --create-database --force

Open http://localhost:8000/admin in your browser after the installation has finished. You should see the Shopware admin interface.

The default credentials are:

• User: admin
• Password: shopware

INFO

When using Windows and WSL2, you need to change the default sales channel domain to http://localhost:8000.

Important: Do use http, not https.

Direnv

If you wish to switch between multiple development environments which use devenv seamlessly, we recommend installing direnv.

When you enter a project directory using devenv, direnv will automatically activate the environment for you. This means you can use the binaries without having to run devenv shell manually, though you still have to run devenv up to start all services.

First, install direnv:

Afterward, add the following hook to your shell:

After you change into a project directory using devenv for the first time, you need to allow direnv to load the environment:

direnv allow

Automatic Shell Activation - devenv.sh

Default services

Here is an overview of services Shopware provides by default and how you can access them:

Service	Access
MySQL	mysql://shopware:shopware@127.0.0.1:3306
Mailhog (SMTP)	smtp://127.0.0.1:1025
Redis (TCP)	tcp://127.0.0.1:6379

Caddy

Caddy is a powerful, enterprise-ready, open-source web server with automatic HTTPS written in Go.

http://127.0.0.1:8000

Adminer

Adminer is a full-featured database management tool written in PHP.

http://localhost:8010

Mailhog

MailHog is an email testing tool for developers.

http://localhost:8025

Customize your setup

To customize the predefined services to match your needs, e.g., changing the virtual host, database name, or environment variables, you can create devenv.local.nix to override the service definitions. It also allows you to add and configure additional services you might require for your local development.

WARNING

After changing devenv.local.nix, please reload your environment.

// <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  # Disable a service
  services.adminer.enable = false;
  
  # Use a custom virtual host
  services.caddy.virtualHosts."http://shopware.swag" = {
    extraConfig = ''
      root * public
      php_fastcgi unix/${config.languages.php.fpm.pools.web.socket}
      file_server
    '';
  };
  
  # Customize nodejs version
  languages.javascript = {
    package = pkgs.nodejs-18_x;
  };

  # Override an environment variable
  env.APP_URL = "http://shopware.swag:YOUR_CADDY_PORT";
}

Refer to the official devenv documentation to get a complete list of all available services and their configuration possibilities:

devenv.nix Reference - devenv.sh

Enable Blackfire

// <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  services.blackfire.enable = true;
  services.blackfire.server-id = "<SERVER_ID>";
  services.blackfire.server-token = "<SERVER_TOKEN>";
  services.blackfire.client-id = "<CLIENT_ID>";
  services.blackfire.client-token = "<CLIENT_TOKEN>";
}

Enable XDebug

// <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  # XDebug
  languages.php.extensions = [ "xdebug" ];
  languages.php.ini = ''
    xdebug.mode = debug
    xdebug.discover_client_host = 1
    xdebug.client_host = 127.0.0.1
  '';
}

Use MariaDB instead of MySQL

// <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  services.mysql.package = pkgs.mariadb;
}

Use customized MySQL port

// <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  services.mysql.settings = {
    mysqld = {
      port = 33881;
    };
  };
  
}

Use customized VirtualHosts port for Caddy

Use customized Adminer port

// <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  services.adminer.listen = "127.0.0.1:9084";
}

Use varnish

# <PROJECT_ROOT>/devenv.local.nix
{ pkgs, config, lib, ... }:

{
  # caddy config
  services.caddy = {
    enable = true;

    # all traffic to localhost is redirected to varnish
    virtualHosts."http://localhost" = {
      extraConfig = ''
        reverse_proxy 127.0.0.1:6081 {
          # header_up solves this issue: https://shopwarecommunity.slack.com/archives/C05CQT51H1V/p1721754934084939
          header_up Host sw.localhost
        }
      '';
    };

    # the actual shopware application is served from sw.localhost,
    # choose any domain you want.
    # you may need to add the domain to /etc/hosts:
    # 127.0.0.1       sw.localhost
    virtualHosts."http://sw.localhost" = {
      extraConfig = ''
        # set header to avoid CORS errors
        header {
            Access-Control-Allow-Origin *
            Access-Control-Allow-Credentials true
            Access-Control-Allow-Methods *
            Access-Control-Allow-Headers *
            defer
        }
        root * public
        php_fastcgi unix/${config.languages.php.fpm.pools.web.socket}
        encode zstd gzip
        file_server
        log {
          output stderr
          format console
          level ERROR
        }
      '';
    };
  };

  # varnish config
  services.varnish = {
    enable = true;
    package = pkgs.varnish;
    listen = "127.0.0.1:6081";
    # enables xkey module
    extraModules = [ pkgs.varnishPackages.modules ];
    # it's a slightly adjusted version from the [docs](https://developer.shopware.com/docs/guides/hosting/infrastructure/reverse-http-cache.html#configure-varnish)
    vcl = ''
      # ...
      # Specify your app nodes here. Use round-robin balancing to add more than one.
      backend default {
          .host = "sw.localhost";
          .port = "80";
      }
      # ...
      # ACL for purgers IP. (This needs to contain app server ips)
      acl purgers {
          "sw.localhost";
          "127.0.0.1";
          "localhost";
          "::1";
      }
      # ...
    '';
  };
}

Use an older package version

Sometimes you want to pin a service to an older version. Here is an example to use a specific mysql version.

{
  services.mysql = let 
    mysql8033 = pkgs.mysql80.overrideAttrs (oldAttrs: {
      version = "8.0.33";
      # the final url would look like this: https://github.com/mysql/mysql-server/archive/mysql-8.0.33.tar.gz
      # make sure the url exists. 
      # alternatively you could use that url directly via pkgs.fetchurl { url = "xyz"; hash="xyz";};
      # for reference see the [different fetchers](https://ryantm.github.io/nixpkgs/builders/fetchers/#chap-pkgs-fetchers)
      src = pkgs.fetchFromGitHub {
        owner = "mysql";
        repo = "mysql-server";
        rev = "mysql-8.0.33";
        # leave empty on the first run, you will get prompted with the expected hash
        sha256 = "sha256-s4llspXB+rCsGLEtI4WJiPYvtnWiKx51oAgxlg/lATg=";
      };
    });
  in
  {
    enable = true;
    package = mysql8033; # use the overridden package
    # ...
  };
}

And another example to use a specific version of rabbitmq-server

{
  services.rabbitmq = let
    rabbitmq3137 = pkgs.rabbitmq-server.overrideAttrs (oldAttrs: {
      version = "3.13.7";
      src = pkgs.fetchurl {
        url = "https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.13.7/rabbitmq-server-3.13.7.tar.xz";
        sha256 = "sha256-GDUyYudwhQSLrFXO21W3fwmH2tl2STF9gSuZsb3GZh0=";
      };
    });
  in
  {
    enable = true;
    package = rabbitmq3137; # use the overridden package
  };
}

Known issues

Manually reloading devenv

If you decided against using direnv, keep in mind that on every change to the *.nix files you need to manually reload the environment. Run exit to quit the current devenv shell and enter the shell again to reload:

devenv shell

Fail to start Redis with locale other than en_US

14:04:52 redis.1           | 364812:M 07 Nov 2023 14:04:52.999 # Failed to configure LOCALE for invalid locale name.

You can export a different locale to your shell with the following command:

export LANG=en_US.UTF8;

FAQ

How do I clean up devenv?

Periodically run devenv gc to remove orphaned services, packages and processes and free-up disk space.

How do I access the database?

The MySQL service is exposed under its default port 3306, see default services.

Be aware that you cannot connect using the localhost socket. Instead, you must use 127.0.0.1.

Where is the database stored?

The database is stored in the <PROJECT_ROOT>/.devenv/state/mysql directory.

Where do I find available packages?

The NixOS package search is a good starting point.

Where do I find the binaries?

The binaries can be found in the <PROJECT_ROOT>/.devenv/profile/bin directory.

This comes in handy if you want to configure interpreters in your IDE.

How do I stop all processes at once?

In case you can't find and stop running devenv processes, you can use the following command to kill them:

kill $(ps -ax | grep /nix/store | grep -v "grep" | awk '{print $1}')

Are you unable to access http://127.0.0.1:8000 in your Browser?

Try using http://localhost:8000 instead. This mostly applies to when using WSL2.

Are you looking for a full test setup with demo data?

Run the below command:

composer setup && APP_ENV=prod bin/console framework:demodata && APP_ENV=prod bin/console dal:refresh:index