Hi,

Been using Aegir Git for site platforms and it works great. I'd like to start using it for sites, but I can't seem to find any docs on what the folder structure for a site git repo should look like.

Should it follow Aegirs?

- files
- libraries
- modules
- themes

etc?

Thanks,
Chris

Comments

c_archer created an issue. See original summary.

helmo’s picture

Category: Bug report » Feature request

Yes that's correct. But I prefer to keep the files dir out of Git...

Example .gitignore file

*~
files
private
settings.php
local.settings.php
drushrc.php

One trick to 'safely' store some $conf settings in Git is to include a file called versioned.settings.php from the local.settings.php

A new 'Git' page under https://github.com/aegir-project/documentation/tree/3.x/docs/usage/advanced might be nice for this info.

c_archer’s picture

Thanks for this :)

Do you want me to write some up on Drupal.org as well?

colan’s picture

@c_archer: All of the official documentation is available at http://docs.aegirproject.org/en/3.x/, which gets automatically updated from GitHub, so we should any new documentation over there. Please use the Edit on GitHub link to submit a merge request, and then we can add your contribution.

Thanks for doing this!

c_archer’s picture

Hi @colan,

This has now been created at: https://github.com/aegir-project/documentation/compare/3.x...chrisarcher...

Thanks,
Chris

colan’s picture

See also: #2879243: Suppressing Creation of a Site 'local.settings.php' File.

Looks like we have several options here.

helmo’s picture

Anyone in favour of auto-including versioned.settings.php just like the local.settings.php? Then there's no need to manually include it, can local.settings.php be used for environment specific overrides, and versioned.settings.php for project specific settings.

colan’s picture

I do think it makes sense to include both: one controlled by Aegir, and the other controlled by Git.