|
@@ -245,7 +245,6 @@ deploy() {
|
245
|
245
|
echo "everything, so few things still need to be done manually."
|
246
|
246
|
echo "This document will guide you throught the rest of the"
|
247
|
247
|
echo "process."
|
248
|
|
-
|
249
|
248
|
echo ""
|
250
|
249
|
echo ""
|
251
|
250
|
echo "Structure"
|
|
@@ -293,7 +292,6 @@ deploy() {
|
293
|
292
|
echo " idea!), be prepared that you will need to follow their"
|
294
|
293
|
echo " guidelines. This will most probably mean huge changes"
|
295
|
294
|
echo " to these packages or even changes to your workflow."
|
296
|
|
-
|
297
|
295
|
echo ""
|
298
|
296
|
echo ""
|
299
|
297
|
echo "Placeholders"
|
|
@@ -357,7 +355,6 @@ deploy() {
|
357
|
355
|
echo " Typical example of a role is e.g. 'bin' for commands"
|
358
|
356
|
echo " (normally under '/usr/bin' or '/usr/local/bin'), 'doc'"
|
359
|
357
|
echo " for documents or 'lib' for libraries."
|
360
|
|
-
|
361
|
358
|
echo ""
|
362
|
359
|
echo " 2. Next, in \`[roots]\` section, you have to set target"
|
363
|
360
|
echo " root directory for each role. However, in order to"
|
|
@@ -366,7 +363,6 @@ deploy() {
|
366
|
363
|
echo " environment variable. For this reason, most paths"
|
367
|
364
|
echo " need to start with \`[ENV:PREFIX]\`."
|
368
|
365
|
echo ""
|
369
|
|
-
|
370
|
366
|
echo " 3. \`[files]\` section is where you assign actual files"
|
371
|
367
|
echo " from your repository to their final paths. The format"
|
372
|
368
|
echo " is \`ROLE = REPOPATH [RENAMED]\`, where ROLE is file's"
|
|
@@ -381,12 +377,10 @@ deploy() {
|
381
|
377
|
echo " individually, if in your repo you have a directory with"
|
382
|
378
|
echo " 100 files of the same role, you can add just path to the"
|
383
|
379
|
echo " directory itself."
|
384
|
|
-
|
385
|
380
|
echo ""
|
386
|
381
|
echo " 4. If some roles require special permissions on your files,"
|
387
|
382
|
echo " \`[modes]\` section is your friend. Permissions here"
|
388
|
383
|
echo " should be in UNIX octal format."
|
389
|
|
-
|
390
|
384
|
echo ""
|
391
|
385
|
echo " 5. Next, \`[tokens]\` section allows you to define own"
|
392
|
386
|
echo " placeholders that will be replaced when your scripts are"
|
|
@@ -396,7 +390,6 @@ deploy() {
|
396
|
390
|
echo " defined here, plus range of tokens automatically defined"
|
397
|
391
|
echo " by MKit. During build, these tokens are replaced with"
|
398
|
392
|
echo " their actual values."
|
399
|
|
-
|
400
|
393
|
echo ""
|
401
|
394
|
echo " 6. Less interesting, but important section is \`[dist]\`,"
|
402
|
395
|
echo " which lists files in your codebase that will be added"
|
|
@@ -404,14 +397,12 @@ deploy() {
|
404
|
397
|
echo " above). Listing directory here will include all its"
|
405
|
398
|
echo " contents, and normally it's OK to be very inclusive, so"
|
406
|
399
|
echo " most of the time this section should be OK."
|
407
|
|
-
|
408
|
400
|
echo ""
|
409
|
401
|
echo " 7. Even less interesting is section \`[ENV]\`. It is"
|
410
|
402
|
echo " special in that it provides *default* value for an"
|
411
|
403
|
echo " environment variable. You almost never need to touch"
|
412
|
404
|
echo " this."
|
413
|
405
|
echo ""
|
414
|
|
-
|
415
|
406
|
echo " 8. Finally, the most interesting section! \`[project]\`,"
|
416
|
407
|
echo " provides most general information for your project such"
|
417
|
408
|
echo " as name and version."
|