Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to structure a python projects with shared sub apps using git and buidout without symbolic links
    primarykey
    data
    text
    <p>I have multiple <strong>projects</strong> that shares child <strong>apps</strong> with other <strong>projects</strong>. When working within the <strong>project</strong> directory I want to be able to make changes to the <strong>app</strong>, update it, and pull those updates into the second <strong>project</strong>.</p> <p>Requirement:</p> <ul> <li>No use of <strong><em>symbolic links</em></strong> (my IDE's debugger doesn't work well with them)</li> <li>No compiling/rerun a script. I would like to make changes to the <strong>app</strong> without having to rerun a script/buildout. </li> <li>Apps must be within the project folder.</li> </ul> <p>Here's the structure:</p> <pre><code>app_one (git repo) |-- app_one (actual app uses by projects) | +-- models.py |-- README.md +-- setup.py project_one (git repo) |-- project_one | |-- apps | | |-- app_one | | | +-- models.py | | | -- app_two |-- setup.cfg +-- setup.py project_two (git repo) |-- project_two | |-- apps | | |-- app_one (same app as project_one) | | | +-- models.py | | | -- app_two |-- setup.cfg +-- setup.py </code></pre> <p>Currently I'm using git-submodules for this; the downside is there is no way to link to a subfolder of a repo. I recently read about subtree, would this work better?</p> <p>Ideally I would like to use <strong>buildout</strong>, but I haven't found a good way to accomplish this without the use of symbolic links. If there's a way to to do this please let me know. </p> <p>Any suggestions would be greatly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload