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

General deployment question #89

Open
pedrodevoto opened this issue Feb 3, 2017 · 2 comments
Open

General deployment question #89

pedrodevoto opened this issue Feb 3, 2017 · 2 comments

Comments

@pedrodevoto
Copy link

Hi. I'm starting to develop sites in Magento and I'm looking for a good and fast way to create new projects. I made some tests with Magestead and it seems to work fine (although I'm having some issues), but the point of this issue is to ask what would be the ideal way to deploy? I usually work with DigitalOcean, and I always create a git repo, push it from my local environment, and pull it from the production server. What is the best way to deploy to production with Magestead? I don't mean to upload the entire Vagrant project to the server, right? I just need to get the public folder up. I'm also kind of new to Vagrant.

Sorry if this question does not belong in an issue, but it is the only way I found to ask!

@richdynamix
Copy link
Owner

Hi,

When you setup your Magestead project it asked you if you wish to add a GIT project. By supplying your GIT repo address, Magestead would initialise the GIT repo and create the initial commit. From here you are free to continue your normal deployment process.

While the contents of your vagrant solution are also stored inside your GIT repo, you should only make the public directory web accessible. Magestead server provisioning is done using PuPHPet. By utilising this provision folder you should be able to provision your Digital Ocean server with the exact same version of software.

@pedrodevoto
Copy link
Author

Thanks, I'll check PuPHPet to see how I can automatically provision the server. Will probably post more Issues regarding some errors I think I found.

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

No branches or pull requests

2 participants