Strangely, with each site creation using Acquia Dev Desktop (which is version 2 of Acquia Dev Desktop), it creates two folders within [Drupal-8-root]/sites.

"default", and "whatever.dd".

The MS Windows 'Right-Click':'Properties' popup windows each of these items shows that they are identically sized.

And, strangely, the icon for the *.dd folder has the little 'shortcut-icon' added to the bottom-left corner of the 'folder-icon'. Very weird.

This double-folder creation was also always the case a couple of years back with the original Acquia Dev Desktop version 1.

I would like to know what the full extent to which the sites/*.dd folder will have a bearing on users. Of particular concern to me is whether or not users can export their sites for use online anywhere other that Acquia's servers.

This confusion is the primary reason why I have not created a beginning newbie users step-by-step guide to using ADDv2 for posting at drupal.org, (similar to the one I created for ADDv1 before I became aware of this issue https://www.drupal.org/node/1248034), even though Acquia Dev Desktop is the easiest way I have found to get a Drupal site up-and-running on Windows (and presumably on MAC).

XAMPP (for Windows, Linux, and MAC)

Instead, I guess I'll look into using XAMPP as an alternative, since it appears to be the 'stack' most highly recommended for Windows across the Earth, and since XAMPP appears to be the Windows stack for which there is the most documentation on drupal.org.

---

@Acquia-Admins
or
@Anybody?

What:
Please post a link where we can find a detailed explanation as to the full extent of in what way the non-standard ways the *.dd folders will immediately affect us as we create our sites; and what will be required of us to export our sites to any number of hosting environments other than Acquia.

Why:
If you would be so kind as to share a link with an explanation as to why this duplicate folder situation exists, that would be wonderful, particularly since my only guess is that it is a proprietary attempt to force users of Acquia Dev Desktop to use Acquia for hosting after they learn too late of their unwitting blindness to this reprehensible fact, assuming my ONLY GUESS is correct, though if I am correct, that surely disappoints me in my desire to truly love Dries Buytaert.

===

Related forum post at acquia.com:

Acquia stack and multisite creates two folders

https://forums.acquia.com/acquia-products-and-services/dev-desktop/acqui...

Comments

sprite’s picture

Why not just install Drupal natively without all the unnecessary commercial baggage?

I run a 64bit XAMPP stack on a Windows 10 machine, with dozens of Drupal 7 and Drupal 8 instances setup as vhosts, with DNS resolved via the etc/hosts file in the windows directory. After proper, detailed, configuration, it is a very workable local dev setup.

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

Christopher James Francis Rodgers’s picture

@Sprite

Thank you for taking time to comment.

XAMMP is, in fact, what I am pursuing now.

Unfortunately, among the dozen or so drupal.org XAMPP pages, I can Not find one that seems to be up-to-date, and which will take a beginner like me through the details of the process.

Kindly, please, what single page (on or off drupal.org) do you recommend?


All the best; intended.
-Chris (great-grandpa.com)
___
"The number one stated objective for Drupal is improving usability." ~Dries Buytaert *

ressa’s picture

I second what sprite says. I use Ubuntu 16.04, and with a Vagrant Scotch Box (version 2.5) I can spin up a local Drupal 8 in a few minutes.

Christopher James Francis Rodgers’s picture

Ressa:

Thanks for you input.

I do not doubt that it would be possible for anyone with enough experience to do as you say.

I am looking for the simplest of local solutions for day-1 absolute beginners-- but also a solution which does not have a limiting nature, nor have any limiting features that might in the future turn out to be desirable for those beginners-of-today who might become 'developers-supreme' in the future.

Seeing that Vagrant has a free version running PHP7, (and aside from the fact, which gives me pause, that it also has a 'Pro' version,) is it not true that both Drupal 7, and Drupal 8, have problems using PHP7?

Would you recommend Vagrant for Windows absolute beginners, or will it likely require a user to perform additional research for non-default configuration changes? Should Windows users expect to experience error/problems based on individual use cases?

Your thoughts are most welcome.


All the best; intended.
-Chris (great-grandpa.com)
___
"The number one stated objective for Drupal is improving usability." ~Dries Buytaert *

sprite’s picture

Install XAMPP using PHP 5.6.x.
Edit the

Then edit the php.ini and my.ini to boost all settings for Drupal adequate, lengthen execution max and increase PHP max memory to at least 512M or more, with 1024M not being unreasonable.

Then edit the - C:\Windows\System32\drivers\etc\hosts - file and add entries



# local domains - including xampp web site virtual hosts

127.0.0.1		localhost 

# example local site names

127.0.0.1		www.localsite0001.lcl
127.0.0.1		www.localsite0002.lcl
127.0.0.1		www.mysite.dd 



Add virtual host entries to httpd-vhosts.conf file.

Example virtual host entry
Note that the virtual hosts are OUTSIDE of the C:\xampp\ directory structure.




<VirtualHost www.localsite.lcl>
  DocumentRoot "C:\local_websites\www.localsite.lcl"
  ServerName www.localsite.lcl
  CustomLog "C:\local_websites\www.localsite.lcl\_logs_\access.log" combined
  ErrorLog "C:\local_websites\www.localsite.lcl\_logs_\error.log"
  <Directory "C:\local_websites\www.localsite.lcl">
	require all granted
    AllowOverride All
  </Directory>
</VirtualHost>



Make sure your vhost runs with a plain index.html to verify server configuration.

Run the composer utility installation on your Windows machine, making it global, (in the PATH).

Download and extract the latest Drupal 8 core code into the docroot of the vhost.
Use the localhost/phpmyadmin utility to create the database for the Drupal website.
From the browser run {site}/install.php and enter database credentials when asked.
Turn of the send email option because you probably don't have a correctly configured local smtp daemon.

Visit the site, login as admin and check the reports.

Update the composer.json file in your site's docroot to something like the following.
Take notice that the Drupal core has been moved from the replace section to the require section.

Example composer.json for the vhost docroot.



{
    "name": "drupal/drupal",
    "description": "Drupal is an open source content management platform powering millions of websites and applications.",
    "type": "project",
    "license": "GPL-2.0+",
    "require": {
        "composer/installers": "^1.0.21",
        "wikimedia/composer-merge-plugin": "~1.3",
        "drupal/core": "8.3.4",

        "drupal/address": "1.x-dev",
        "drupal/commerce": "2.x-dev",
        "commerceguys/intl": "v0.7.4",

        "drupal/admin_toolbar": "1.19.0",        
        "drupal/module_filter": "3.0.0"
    },
    "replace": {
    },
    "minimum-stability": "dev",
    "prefer-stable": true,
    "config": {
        "preferred-install": "dist",
        "autoloader-suffix": "Drupal8"
    },
    "extra": {
        "_readme": [
            "By default Drupal loads the autoloader from ./vendor/autoload.php.",
            "To change the autoloader you can edit ./autoload.php."
        ],
        "merge-plugin": {
            "include": [
                "core/composer.json"
            ],
            "recurse": false,
            "replace": false,
            "merge-extra": false
        }
    },
    "autoload": {
        "psr-4": {
            "Drupal\\Core\\Composer\\": "core/lib/Drupal/Core/Composer",
            "Drupal\\composer_manager\\Composer\\": "modules/composer_manager/src/Composer"
        }
    },
    "scripts": {
        "pre-autoload-dump": "Drupal\\Core\\Composer\\Composer::preAutoloadDump",
        "post-autoload-dump": "Drupal\\Core\\Composer\\Composer::ensureHtaccess",
        "post-package-install": "Drupal\\Core\\Composer\\Composer::vendorTestCodeCleanup",
        "post-package-update": "Drupal\\Core\\Composer\\Composer::vendorTestCodeCleanup",
        "drupal-rebuild": "Drupal\\composer_manager\\Composer\\Command::rebuild",
        "drupal-update": "Drupal\\composer_manager\\Composer\\Command::update"
    },
    "repositories": {
        "drupal": {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    }
}



Run "composer install" in the vhost docroot and it will update the site to the configuration defined in the composer.json.

In your browser run {site}/update.php.

You will then have a complete up to date basic Drupal instance.

To use the Drupal 8 admin_toolbar and the module_filter modules, go to the admin extend page and enable them.

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

ressa’s picture

@Christopher James Francis Rodgers: I haven't used Windows since 2008, so I am probably not the right person to ask. But as far as I understand, it is possible to use Vagrant in VirtualBox on Windows. See this article for more info:

https://www.jeffgeerling.com/blog/2016/developing-virtualbox-and-vagrant...

But XAMPP will probably work just as well for you. What I really like with Vagrant is that I can spin up a fresh server very quickly, and delete it after I have finished my task.

Scotch Box is just one of many Vagrant distributions, you can read more about them here: https://www.vagrantup.com/docs/boxes.html

It is true that the latest Scotch Box 3.0 is a paid ("Pro") service, but the previous one (Scotch Box 2.5) comes with Ubuntu 14.04 and is still free.

So in short, probably start with XAMPP, since it has a lower entry level. But I would also encourage you to test Windows + VirtualBox + Vagrant, and see if it might work for your, and share your experience here.

sprite’s picture

A XAMPP setup on Windows 10 64bit is a robust and easy to maintain platform.

For proper performance, a ton of ram is helpful, as is a SSD for storage of all XAMPP components and all Drupal website files, since Drupal is completely disc activity heavy, and needs SSD read speed plus caching afforded by large memory.

With Windows 10 Pro is is also possible to run any Linux distro around, and on some machines even MacOS, in virtualization.

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

richardbmcdonald’s picture

I am brand new to Drupal too and also to website development. I at first tried Aquia, but found it overly complex and odd for the same reasons as you. I am blind, and found it pretty inaccessible. On the other hand, I found XAMPP much easier to install and use; though not TOTALLy accessible. After some initial trouble installing Druopal, I finally got it installed siimply using the drupal.org instructions for installing Drupal under XAMPP.

Nick Hope’s picture

This second  folder is a junction. It just mirrors the contents of the default folder. I suppose it's in there for some functionality that Dev Desktop requires. As far as I can tell, you can just ignore it. I'm setting my .gitignore file to ignore it too.