Being a massive fan of Drupal Pro (I can see no reason why anyone on Mac or Windows would use anything else for Drupal work), it was great to see the meta issue about feature requests. I am going open issues for a few obvious ones.

Provide the latest release of Drupal 8 (even if still in alpha) and Drush 7.

Comments

mike stewart’s picture

mike stewart CreditAttribution: mike stewart commented
Status: Active » Postponed
Parent issue: » #2195619: Meta Issue: Drupalpro Version 2 Feature Requests

Ah, wish I had seen this one first. lol. damn, saw them all in the queue, and really appreciate the feedback, and might have answered the others a little differently. But I'm glad I mostly approached in the spirit I think they were intended. Thanks again for the feedback!

re: Drupal8. totally agree. consider it done ... no way I'm shipping a next version without D6/D7D8 ready to install via drush

Roden’s picture

Roden CreditAttribution: Roden commented

Drupal 8 beta has been released, any chance for that new DrupalPro version yet?

John_B’s picture

John_B CreditAttribution: John_B commented

Some overlap with this? https://www.drupal.org/project/vdd

EDIT I deleted my copy of Drupal Pro because ibdata1 got huge (maybe set innodb_file_per_table next time...), and tried working with VDD. Could not get it working on Windows, and have posted to the issue queue. So for non-Linux users it may not be a useful alternative to Drupal Pro. There is a list of other Vagrant-based VMs here https://www.drupal.org/project/vm

Roden’s picture

Roden CreditAttribution: Roden commented

Not sure in regards to overlap, but I'm more familiar with the DrupalPro setup and it's worked well for me up until now.

So why would ibdata1 getting huge mean you have to delete DrupalPro? According to this, it looks fairly easy to purge.. http://stackoverflow.com/questions/3456159/how-to-shrink-purge-ibdata1-file-in-mysql

Couldn't you also just add more space to your virtual box image?

Though you do bring up a point with "innodb_file_per_table" - this is not set by default on MySQL 5.5. If I set my my.cnf to the following:

[mysqld]
innodb_file_per_table

Would there be any performance implications? i.e. why shouldn't I set this right now before my ibdata1 grows even larger?

John_B’s picture

John_B CreditAttribution: John_B commented

I could have purged it. The whole VM had got too bloated on my small SSD. I do like DrupalPro. I tried a few of the many linked VMs at https://www.drupal.org/project/vm and had various troubles with them. I went to https://puphpet.com/ and made my own VM configuration using the configurator, which can automate install of drush & other packages. It is working fine. Nevertheless, like those linked VMs in the list, it is a less complete solution than DrupalPro. It lacks desktop & related tools, which means you need to set up your Windows / Mac hosts file; and I had to do my own CLI Apache config, and download Drupal; so it is less quick and less suitable for beginners than DrupalPro (though I guess Drupal increasingly attracts more experienced developers on larger projects).

mike stewart’s picture

mike stewart CreditAttribution: mike stewart commented

Hi - yes I'm working on a *new* version of Drupalpro based on vagrant/puppet, many updates... and more so, the fact its based on puppet, should make it easier to update ... as well as use/modify easily for production.

I'll try to post a link to the public repo for a alpha version within a week. I just have two small projects to finish up this week first -- one of which is very related to this work in progress.

Roden’s picture

Roden CreditAttribution: Roden commented

Great to hear that Mike! Looking forward to it. I don't like to push you on updates - but I think everyone will agree having a release for D8 is quite important!

jslundberg’s picture

jslundberg CreditAttribution: jslundberg commented

Looking forward to seeing the next version. As I learn Drupal, DrupalPro has become my default starting point. Thanks so much.

Roden’s picture

Roden CreditAttribution: Roden commented

Hey everyone - hope you're having a great Christmas and new year. A little update from me: I managed to try Drupal 8 out with vagrant using the link John_B posted (https://www.drupal.org/project/vdd) and so far its been pretty smooth sailing. By default it seems to mount the sites folder in Windows, which seems very handy at the beginning but people have said this is incredibly slow, so I disabled that.. usually I just use Git for transferring site files (with SFTP as backup). SFTP works fine (by default it accepts localhost:2222 u:vagrant p:vagrant).

Now I'm trying to setup ssh keys for Git like I did with DrupalPro which as I understand is a little more complex than usual with Vagrant, I'll try to let you know how it goes. Have not tested site performance yet either, but the default D8 setup with default PHP/caching settings seems to work fine/is snappy enough.

I just post all this in case anyone wants to use an updated VM before the next version of DrupalPro arrives (as I'm not sure when that will happen, and the new year is rapidly approaching). If you have any tips please feel free to share! :) I have a feeling there will be a few bumps on the road (still yet to reach things such as rvm etc)!

Also another thing - you probably want to know how to add/destroy sites on the fly without deleting the whole VDD VM (as the site setup is loaded from a config file when you first create the VM).. here's how to do that:

1. First add the new site config into your config.json file (the format is simple and understandable by anyone)
2. Type the command "vagrant global-status" to see the IDs of all your vagrant set ups.
3. Type the command "vagrant reload id-number-here --provision"
4. Follow the instructions at http://192.168.44.44 to setup a Drupal install for that new site.

That should do it.. though I'm still new to Vagrant, I think this is the correct way to do it so all aliases for new sites work correctly.

I also understand what you mean by bloated now, John_B. My DrupalPro is currently like 17GB, and the new VDD setup is like 2GB with 80GB capacity (I guess it expands as I fill it?).

John_B’s picture

John_B CreditAttribution: John_B commented

The bloat is a general issue with mysql when not using the innodb_file_per_table setting. It would be good if this were fixed in a future version of DrupalPro. In the meanwhile your option is to live with it, or to dump your databases, set the innodb_file_per_table setting, destroy you databases, restart mysql (or reboot) and re-import your databases. Which is kind of a pain. For more detailed guidance on fixing it, Google for the problem of large database files when using Innodb and the file per table setting.

webdrips’s picture

webdrips CreditAttribution: webdrips commented

Would love to see a D8-ready release soon because I want to provide a bunch of D8 module ports...any word on the progress?