Browse Source

usage repo

master
test2 5 years ago
parent
commit
3a4d72d474
  1. 60
      index.adoc

60
index.adoc

@ -17,7 +17,7 @@ include::header.adoc[]
{empty} + {empty} +
This HowTo teaches you how to use Services on SwarmLab. The followin HowTo shows how services are used in swarmlabs!
== What is swarmlab.io? == What is swarmlab.io?
@ -45,7 +45,63 @@ The goal of this project is to provide the easiest, fastest, and most painless w
=== http://docs.swarmlab.io/SwarmLab-HowTos/HowTo-gitea.adoc.html[HowTo-create Repo] === http://docs.swarmlab.io/SwarmLab-HowTos/HowTo-gitea.adoc.html[HowTo-create Repo]
=== http://docs.swarmlab.io/SwarmLab-HowTos/HowTo-create-lab.adoc.html[HowTo-create_and_Run Lab Instance] ==== Repo Directory_Structure_4_Lab_Instance
Lab_Instance first clones your Repo and then automatically loads certain files based on a known file
structure.
.Directory_Structure
[source,bash]
----
swarmlab/
├── run
├── runafter
└── runbefore
----
===== runbefore
Lab_Instance dependencies. "runbefore" allows you to automatically pull-in other dependencies when using a Lab_Instance. This file should contain a list of tasks and parameters to insert before the specified repos are executed on Lab_Instance.
===== run
Contains the main list of tasks to be executed by the Lab_Instance.
===== runafter
Lab_Instances is the machanism that allows you to to permanently save your data.
Lab_Instances are mortal, and it’s pretty much routine them to be stoped and deleted.
If you have something like a data/log file that needs to be saved then at this point make sure to back it up!
[NOTE]
====
You can use any Script Programming Language you want to automate the
execution of Lab_Instance
The shebang **MUST** be in the first line
.e.g.
[source,bash]
----
#!/usr/bin/perl
use strict;
use warnings;
print "hello world!\n";
----
====
=== http://docs.swarmlab.io/SwarmLab-HowTos/HowTo-create-lab.adoc.html[HowTo-create_and_Run Lab_Instance]

Loading…
Cancel
Save