Jump to content

Recommended Posts

So I've decided to make the jump to Vagrant...leaving my beloved XAMPP behind. I was initially drawn to Scotchbox but it comes with some stuff that I don't need need - Laravel, all the node stuff as well as the caching stuff - and I couldn't find info whether it is customisable. My plan is to use either PuPHPet or Protobox  (edit: I'll stick with PuPHPet) to customise my box the way I want. Either that or just install things manually (much like I set up my remote server)...I have done my reading and watched YouTube videos so I feel I am ready to take the plunge. I only need one machine (much like what I was doing with XAMMP) so will not be destroying anything soon. The most important things to me (apart from the LAMP stack of course) are automated DB backups and an environment where XDebug can work. I've never been able to have the thing work in XAMPP/Windows! Slightly OT but I might be ditching Sublime Text 3 in favour of Visual Studio Code. Tried it recently and was very impressed...if only Xdebug would work! (before you say it, yes, Tracy is nice for all other needs but what I want as well is something I can use to step through code)....OK, wish me luck... :-)

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites

jep, only thing to be REALLY careful when using vagrant is to have proper DB dumps available on your filesystem. otherwise you are lost, when your box crashes for whatever reason.

the vagrant triggers plugin is a good tool. just write a little backup skript (https://github.com/BernhardBaumrock/vagrant-pw-lamp/blob/master/bin/db_backup) and it will call that on every vagrant halt or destroy.

i wish you good luck ;) looking forward to hearing your learnings

  • Like 1

Share this post


Link to post
Share on other sites

@Bill C

Depending on your knowledge in managing linux servers Docker might not be a good fit. It does make things easier for experienced people, but if you're just getting into it it's just another complex layer. 

Good point LostKobrakai, thank you for the warning! :) . I'll leave it on my 'List' for reference, but I think I'll give Vagrant another go soon when I have some time. And thanks to bernhard , gurkendoktor ,  MindFull and  kongondo  for your thoughts and recommendations.

Share this post


Link to post
Share on other sites

I left Vagrant in favor of my LAMP setup, as I develop on Linux (actually openSuse right now).

I could NOT get Vagrant and my Gulp setup to work, particularly Browser-Sync. While everything else worked as expected, I could not figure this out. But that's okay. My LAMP setup closely matched my Digital Ocean box.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By DanielKit
      Hi. I'm currently stuck at the login page in my project. Once I enter my admin username and my password and press login, nothing happens. The page just reloads. However, the URL changes from http://myipaddress/processwire to http://myipaddress/processwire/?login=1. I've checked all of my server settings, and to my knowledge, all seems to be fine there. I don't know where to go from here.. Thanks in advance!
    • By rickm
      Hey all,
      A while back I was trying to get Processwire working on the Homestead vagrant box - a really handy vagrant box made by Taylor Otwell (Laravel creator). One cool thing about homestead is it has its own config file where you can set 'path maps' which map a folder on your computer to the vagrant box, and then also set up hostnames. So for example you can set up 10 domains pointing to different locations on your machine, making it a nice all in one vagrant development box for your sites. 
      One thing it didn't do was support processwire. The way it works is it uses setup files for each site, and you can specify things like a site to use nginx, a site to use apache, etc. 
      So to get round this I wrote a custom setup script for it to get processwire working, and it works really well. I've put it up on github should anyone else find it handy, it's a pretty simple little script and is based on the Laravel one included in Homestead.
      Hopefully it'll be useful to someone out there  You can grab it here: https://github.com/rickmills/homestead-processwire
    • By thmsnhl
      Hi everybody,
      we started our first Processwire driven project in my new company and for the first time, I was working on one site with more than 2 colleagues on the same site.
      It didn't take long for us to stumble across some problems when multiple developers work at the same time, conflicts with updating the database on vagrant machines, like duplicate entries for page IDs, errors when setting up fields and stuff like this. We ended up working on a dedicated database server, that we linked to our vagrant machines and most of the problems were gone, but the performance of this constellation is really bad compared to our first approach with database running on vagrant machines.
      I already tried to find a solution in the forums but I couldn't find anyone with problems like this.
      So I was wondering: how do you manage projects with multiple developers on vagrant machines in a git-based workflow?
    • By FrancisChung
      Unfortunately, this magazine has bitten the dust but they were gracious enough to have their entire back catalogue available for download.
      https://secure2.linuxjournal.com/pdf/dljdownload.php
×
×
  • Create New...