Great work on VDD! I am running into an issue in two areas with Drupal 8.
1) when I try to install a new module it's asking me to enter my ftp information, and then when I enter my credentials to the box, update manager comes up prompting me to enter FTP credentials. This never happened when I used a webhost.
2) if I try to create an article and add an image, I get "The file could not be uploaded."
All I have done so far is "vagrant up" and installed drupal 8 according to the instructions provided.
Is there anything I'm missing here?
Thanks,
Scromie
Comments
Comment #1
scromie commentedHas anyone had a chance to look at this?
Comment #2
videographics commentedI agree. VDD is super-useful. But as far as I can tell, anyone using VDD is going to encounter the following warnings when trying to install a module from the modules page:
Comment #3
videographics commentedI've only encountered and tested this with D7. Unsure if this happens in D8.Here's how to fix this problem by installing ftp and enabling it for authenticated users:
Make sure your vagrant vm is running. Then:
Edit the ftp config file to enable authenticated users to ftp:
Then uncomment the following lines:
Save the file. (Control-x, y, return) Restart ftp with:
After this, you should be able to install modules from the modules page. Login with "vagrant" for the username and password if/when asked.
Obviously, it'd be best if we didn't have to do this.
Comment #4
druplicate commentedThis is not the preferred way to install modules as it's not secure.
The vast majority of developers use Drush. VDD includes Drush aliases to make it easy.
Comment #5
videographics commentedOn a local vm, this really shouldn't be a security issue. We're already running ssh with vagrant/vagrant and mysql with root/root. (Most of us are running nfs as well.) ftp isn't going to make a difference.
Yes, most of us use drush most of the time to install modules, but if installing from the modules page it's a valuable enough function to be included in drupal core, it should be supported here. If vdd's design goal is to create a seamless working dev environment for Drupal, it's pretty bad form to have it intentionally breaking a core capability of D7.