-
Notifications
You must be signed in to change notification settings - Fork 3
Drop Vagrant box in favour of Docker #24
Comments
As long as there are adjusted docs for it that sounds like a good move. I am not on any project with Docker so I am guessing that there are also other people who will need some guidance. |
Could this be useful? https://github.com/laradock/laradock |
Also we need to make sure we don't hit any performance issues like we did for SweepBright. Apart from that i'm all in! 👍 |
I think we have our own that Tony set up. I'm not too sure what performance issues we experienced but maybe @tonysm can advise us on what we should do since he seems to be the resident expert :) |
If you guys prefer to use that, that's useful. Docker containers are easy to build, so that's why we don't see lots of abstractions on it. We can document the process to setup the laradock globalally (one config for all projects), as described here: http://laradock.io/#B
That's tricky because it's only a Mac issue. But I think a project like Laradock, which is maintained by the community might have already tackled this, since lots of developers use Mac. Worth a try. On Friday, I'm going to switch the Sweepbright project to use Laradock instead, but I'm going to need someone with a Mac to test and before/after of that. |
@tonysm count me in to test if you need! |
I've done some testings with laradock, like it, since it has most of the containers we would need for development. Here's a guide: https://gist.github.com/tonysm/e16fbc270148b3180e89819cab7df6cc |
Seeing as we're installing docker on existing projects and using Vagrant less and less maybe it makes sense to support Docker out of the box via skeletor?
The text was updated successfully, but these errors were encountered: