B
B
Bojczuk2016-03-03 12:15:13
git
Bojczuk, 2016-03-03 12:15:13

Structure of repositories for fast delivery to combat vehicles?

The test server has the following (non-final) application structure:

  • common_files
  • app1
  • app2
  • app3


Each app has the same codebase, some templates and statics, only 10 template files and a couple of static files differ. In each of these directories there are symlinks to files from common_files.
Each app must be delivered to its specific battle server.

But how to organize repositories so that each of them contains common_files and a specific app? Or is it better to make separate branches for each app?
Or maybe it's worth reorganizing the file structure? Any advice and ideas are welcome.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
D
DevMan, 2016-03-03
@Bojczuk

appX in separate repacks.
common_files is also in a separate file and tied to the rest using submodule/subtree.

S
sim3x, 2016-03-03
@sim3x

Do not use symlinks Separate
general into a separate app
Use import
Use pip install

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question