Installing A* on OpenBSD
The simplest way to get started is to run the following command in a fresh install of OpenBSD.
ftp -o - http://localhost:4317/install.sh | shINSTALL - bootstrapping A*
Section titled “INSTALL - bootstrapping A*”This section describes the initial setup of A* in a user account.
Preparation: machine setup
Section titled “Preparation: machine setup”- Setup an OpenBSD machine using either a standard
OpenBSD install (see
platform-openbsd-laptop) or a virtual machine (seeplatform-openbsd-vm). - Add a user account noting the username will be the same as your A* user identifier. Do not use use spaces or other symbols please.
- Set the shell to
bash - Ensure the password is strong and remote access is limited.
Preparation: A* account setup
Section titled “Preparation: A* account setup”Contact an A* Administrator (Phil for now) and provide:
- Username - note that we need to keep these unique
- Proposed roles/purpose, e.g.
- a-team member
- a-user member
- etc..
- Note that each component has its own set of roles
for each user, e.g.
davem: developer access to all components.dennis: read and ticketting access to all components.
The system provides a fine grained set of roles/capabilities
(see RBAC) but in general we use:
developer - able to read and write a component.
reader - read only access to a component.
manager - read only access plus the ability to read/write
Tickets, Forum, etc.
Create working directory
Section titled “Create working directory”Create a working directory, typically:
% mkdir ~/asNote that you can have more than 1 working directory but you will need to update the variables we set in the next two sections.
Setup .profile
Section titled “Setup .profile”Add the following paths where as is your working directory.
export ASTAR=$HOME/asexport PATH=$ASTAR/bin:$PATHexport MANPATH=$ASTAR/man:$MANPATHSetup .bashrc
Section titled “Setup .bashrc”You may want to update your setup with a few aliases.
alias make=gmakealias f=fossilalias c="fossil commit"alias d="fossil gdiff --tk --tclsh /usr/local/bin/tclsh8.6"alias r="d;c;t"Setup the initial working and clone
Section titled “Setup the initial working and clone”We need to install a-clone to do the initial cloning/copying
of the components. a-clone is implemented as a standalone
program that specifically does not depend on any of the
other A* components.
% cd $ASTAR% pwd% mkdir -p bin lib share man sbin include% f clone https://$USER@a-star-microgrid.com/as/components/a-clone% cd a-clone% make installThe simplest case of cloning all components you have access to is:
% a-cloneThis will download each component and setup
component-name.fossil which is the fossil
repository database and component-name containing
the actual checked out version.
Using A* locally
Section titled “Using A* locally”- Describe FOSSIL_USER variable
- Describe ASTAR_PASSWORD variable
- Bin/lib/… packager - rather than use the direct components we could make up meta components that setup bin/lib/… so that everyone doesn’t need access to the source components.