Difference: ACSWorkshop2014GroupExercise (3 vs. 4)

Revision 42014-08-28 - JonathanAntognini

Line: 1 to 1
 
META TOPICPARENT name="ACSTrainingCourse"

Group Exercises

Line: 30 to 30
 
    • Simply run echo $SHELL and check that the output reads /bin/bash

Setting up the ACS environment variables

  1. Create a .acs directory
Changed:
<
<
    • run cp -r /alma/ACS-2014.2/ACSSW/config/.acs $HOME
>
>
    • cp -r /alma/ACS-2014.2/ACSSW/config/.acs $HOME
 
  1. Source the ACS bash profile
    • add the following lines to your $HOME/.bashrc file
Line: 55 to 55
 
  1. Start the tools from the Tools menu. Object Explorer and Logging Client in particular. Alternatively you can start the tools from the command line with the following commands: objexp, jlog
  2. Activate and deactivate ACS components from the object explorer
Changed:
<
<
  1. Stop ACS and all running containers by pressing the stop button on the GUI or using the command
line: acsStop
>
>
  1. Stop ACS and all running containers by pressing the stop button on the GUI or using the command acsStop
 

Group Exercise #2: Setting up a development environment

Setting up the your local git repository

Git is used as the source code repository. Below are the elementary working commands. A more complete git commands reference is here. Before you start you need to define your git user name (same as development account) and e-mail:
Line: 75 to 75
 And to push your changes back to the central server (and make them available to others):
  • git push
If you are not sure you can always check the change status:
Changed:
<
<
  • git status
>
>
  • git status
 

Setting up your INTROOT area

Create an integration root area for your personal account (INTROOT) by issuing the following commands:
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback