For some years now, I have been using Laravel Homestead to quickly build up a virtual machine with all I needed installed. But it seems to not quite get the love it needs, and I’m wondering if folks have moved on to a different environment or tool for their development.

  • chiisanaA
    link
    146 months ago

    The industry by and large have moved on to containers, with docker being the entry point and eventually graduating to something larger and more orchestrated like k8s.

    You’d generally use a publisher container (I.e. php:latest), and then volume mount your code into it for development, and eventually baking your own image for deployment. Be mindful to not include secrets (API keys, passwords, etc.) and inject them via environment variables.

  • shnizmuffin
    link
    fedilink
    English
    46 months ago

    Hey, you should take a look at how Laradock works. I install it as a submodule when I’m working on PHP applications. Slaps the shit out of Laravel Sail and keeps the core dependencies off my OS.

  • @hperrin@lemmy.world
    link
    fedilink
    36 months ago

    For development, I just run node on my system. I use a library called Nymph.js (that I developed) that runs on SQLite in development, then either MySQL or Postgres in production. It’s nice because I can sync my dev db with rsync when I need to test on a cloud machine, and db backups are really small and easy to manage (literally just copying a few files).

  • @GreenKnight23@lemmy.world
    link
    fedilink
    019 days ago

    docker.

    get it, use it, learn how to quickly turn up and blast away environments.

    I’ve built an entire ecosystem/toolbox out of containerized tools.

    It’s reduced my delivery times by 50% and decreased my on-the-job stress by a lot.

    I don’t have to worry anymore of library version collisions. no more asking “what version node am I on?” or “does rvm/nvm support this version?”

    I’ve also been using it to develop AWS cloud services locally as well. Don’t need to deploy and increase costs if I can replicate the services locally. testing has become an absolute breeze.

    • @psion1369@lemmy.worldOP
      link
      fedilink
      019 days ago

      I’ve actually started using Docker/Podman in my own environment, but I’m curious how you use it to develop AWS services with it.

      • @GreenKnight23@lemmy.world
        link
        fedilink
        119 days ago

        there are images available based on some of the services.

        dynamodb, lambda, most other services are simply http mocks like secrets, apigw, sqs, sns, etc. there are others, like documentdb, that are based on other products(mongodb) that can be used in its place.

        the only thing you can’t really replicate is IAM users/roles.