git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Help planning a git repo layout

From
LGLeevi Graham <info@leevigraham.com>
Date
Sep 18, 2008, 08:37 UTC
Message-ID
<938E7E5C-4FCB-4131-A5C4-254CEEC70673@leevigraham.com>
Hey everyone,
I'm after some advice on how to layout my git repo(s).
Here's my current situation:

I am developing 10 different ExpressionEngine addons that all live inside one ExpressionEngine installation. A simplified EE installation has the following folders (all cruft removed):

|-root
   |-ee-admin
   |---extensions
   |---language
   |---modules
   |-themes
   |---site_themes

My addons are a combination of files located in the extensions, language, modules and themes folders. An simple extension may look like:

|-root
   |-ee-admin
   |---extensions
   |-----ext.lg_data_matrix.php
   |---language
   |-----english
   |---------lang.lg_data_matrix.php
   |---modules
   |-themes
   |---site_themes
The extension above contains two files:
- /ee-admin/extensions/ext.lg_data_matrix.php
- /ee-admin/language/english/ext.lg_data_matrix.php

I will be developing multiple extensions in the one EE install to make sure they all work with the core and do not conflict with each other. So my directory will have more than one addon in it:

|-root
   |-ee-admin
   |---extensions
   |-----ext.lg_data_matrix.php
   |-----ext.lg_minify.php
   |-----ext.lg_better_meta_ext.php
   |---language
   |-----english
   |---------lang.lg_data_matrix.php
   |---------lang.lg_minify.php
   |---------lang.lg_better_meta.php
   |---------lang.lg_better_meta_ext.php
   |---modules
   |-----lg_better_meta
   |---------mcp.lg_better_meta.php
   |---------mod.lg_better_meta.php
   |-themes
   |---site_themes

My problem comes when I want to tag and release an individual addon which is a collection of files in multiple folders.

Just say I wanted to tag and release LG Better Meta. Ideally I would like to export a folder structure like:

- /ee-admin/extensions/ext.lg_better_meta.php
- /ee-admin/language/english/ext.lg_better_meta.php
- /ee-admin/language/english/ext.lg_better_meta_ext.php
- /ee-admin/modules/lg_better_meta/mcp.lg_better_meta.php
- /ee-admin/modules/lg_better_meta/mod.lg_better_meta.php

I would also like to give people the ability to clone each of the addons either as a full repo or part thereof.

Any advice would be greatly appreciated.
Cheers Leevi
Next: Boaz Harrosh
Message 1 of 3 in “Help planning a git repo layout”
  1. Leevi GrahamSep 18, 2008
  2. Boaz HarroshSep 18, 2008
  3. Boaz HarroshSep 18, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.