Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Vagrant integration and promote Homestead instead #342

Open
wouterj opened this issue Aug 4, 2016 · 4 comments
Open

Remove Vagrant integration and promote Homestead instead #342

wouterj opened this issue Aug 4, 2016 · 4 comments
Assignees

Comments

@wouterj
Copy link
Member

wouterj commented Aug 4, 2016

Homestead supports Symfony applications. It would be very simple to get the CMF running using homestead.

Should we remove the vagrant integration from this repository and instead write a small piece of documentation about homestead?

/cc @symfony-cmf/core

@wouterj wouterj added the DX label Aug 4, 2016
@wouterj
Copy link
Member Author

wouterj commented Aug 4, 2016

Please note that the current vagrant integration is not really great: #266 , #294

@dbu
Copy link
Member

dbu commented Aug 4, 2016

if that is what symfony itself is recommending as virtualization, then i agree. we should try to follow symfony core with that as closely as possible. both convenient for devs used to symfony and for us to not have to figure out things but just port from symfony.

@ElectricMaxxx
Copy link
Member

Shouldn't we wait until SensioCloud is out and grab somethin symfony related process then?

@dbu
Copy link
Member

dbu commented Dec 2, 2016

does sensio cloud work locally? do people need to create an account? i'd rather have something open source here than a commercial product. i'd expect that the sensio cloud setup instructions for core symfony should just be applicable to the cmf as well. ah, maybe jackrabbit would need some effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants