1 # XDS - X(cross) Development System Server
3 `xds-server` is a web server that allows user to remotely cross build applications.
5 The first goal is to provide a multi-platform cross development tool with
6 near-zero installation.
7 The second goal is to keep application sources locally (on user's machine) to
8 make it compatible with existing IT policies (e.g. corporate backup or SCM),
9 and let user to continue to work as usual (use his favorite editor,
10 keep performance while editing/browsing sources).
12 This powerful and portable webserver (written in [Go](https://golang.org))
13 exposes a REST interface over HTTP and also provides a Web dashboard to configure projects and execute _(for now)_ only basics commands.
15 `xds-server` uses [Syncthing](https://syncthing.net/) tool to synchronize
16 projects files from user machine to build server machine or container.
18 > **NOTE**: For now, only Syncthing sharing method is supported to synchronize
19 projects files. But in a near future and for restricted configurations, `xds-server`
20 will also support "standard" folder sharing (eg. nfs mount points or docker
23 > **SEE ALSO**: [xds-exec](https://github.com/iotbzh/xds-exec),
24 wrappers on `exec` commands that allows you to send commands to `xds-server`
25 and for example build your application from command-line or from your favorite
26 IDE (such as Netbeans or Visual Studio Code) through `xds-server`.
30 `xds-server` has been designed to easily compile and debug
31 [AGL](https://www.automotivelinux.org/) applications. That's why `xds-server` has
32 been integrated into AGL SDK docker container.
34 >**NOTE** For more info about AGL SDK docker container, please refer to
35 [AGL SDK Quick Setup](http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/setup-sdk-environment.html)
39 Load the pre-build AGL SDK docker image including `xds-server`:
42 seb@laptop ~$ wget -O - http://iot.bzh/download/public/2017/XDS/docker/docker_agl_worker-xds-latest.tar.xz | docker load
47 You should get `docker.automotivelinux.org/agl/worker-xds:X.Y` image
50 # List image that we just built
51 seb@laptop ~$ docker images | grep worker-xds
53 docker.automotivelinux.org/agl/worker-xds 3.99.1 786d65b2792c 6 days ago 602MB
56 ### Start xds-server within the container
58 Use provided script to create a new docker image and start a new container:
62 seb@laptop ~$ wget https://raw.githubusercontent.com/iotbzh/xds-server/master/scripts/xds-docker-create-container.sh
64 # Create new XDS worker container
65 seb@laptop ~$ bash ./xds-docker-create-container.sh
67 # Check that new container is running
68 seb@laptop ~$ docker ps | grep worker-xds
70 b985d81af40c docker.automotivelinux.org/agl/worker-xds:3.99.1 "/usr/bin/wait_for..." 6 days ago Up 4 hours 0.0.0.0:8000->8000/tcp, 0.0.0.0:69->69/udp, 0.0.0.0:10809->10809/tcp, 0.0.0.0:2222->22/tcp agl-xds-seb@laptop-0-seb
73 This container (ID=0) exposes following ports:
75 - 8000 : `xds-server` to serve XDS Dashboard
79 #### Manually setup docker user id
81 If you plan to **use path-mapping sharing type for your projects**, you need to have the same user id and group id inside and outside docker. By default user and group name inside docker is set `devel` (id `1664`), use following commands to replace id `1664` with your user/group id:
83 # Set docker container name to use (usually agl-xds-xxx where xxx is USERNAME@MACHINENAME-IDX-NAME)
84 seb@laptop ~$ export CONTAINER_NAME=agl-xds-seb@laptop-0-seb
86 # First stop xds-server
87 seb@laptop ~$ docker exec ${CONTAINER_NAME} bash -c ""
89 # Change user and group id inside docker to match your ids
90 seb@laptop ~$ docker exec ${CONTAINER_NAME} bash -c "usermod -u $(id -u) devel"
91 seb@laptop ~$ docker exec ${CONTAINER_NAME} bash -c "groupmod -g $(id -g) devel"
93 # Update some files ownership
94 seb@laptop ~$ docker exec ${CONTAINER_NAME} bash -c "chown -R devel:devel /home/devel /tmp/xds"
98 **`xds-server` is automatically started** as a service on container startup.
100 If the container is running on your localhost, you can access the web interface (what we call the "Dashboard"):
103 seb@laptop ~$ xdg-open http://localhost:8000
106 If needed you can status / stop / start it manually using following commands:
109 # Log into docker container
110 seb@laptop ~$ ssh -p 2222 devel@localhost
113 devel@docker ~$ sudo systemctl status xds-server.service
116 devel@docker ~$ sudo systemctl stop xds-server.service
119 devel@docker ~$ sudo systemctl start xds-server.service
121 # Get XDS server logs
122 devel@docker ~$ sudo journalctl --unit=xds-server.service --output=cat
125 ### Manually Start XDS server
127 XDS server is started as a service by Systemd.
130 /lib/systemd/system/xds-server.service
133 This Systemd service starts a bash script `/usr/local/bin/xds-server-start.sh`
135 If you needed you can change default setting by defining specific environment
136 variables in `/etc/default/xds-server`.
137 For example to control log level, just set LOGLEVEL env variable knowing that
138 supported *level* are: panic, fatal, error, warn, info, debug.
141 seb@laptop ~$ ssh -p 2222 devel@localhost
142 devel@docker ~$ echo 'LOGLEVEL=debug' | sudo tee --append /etc/default/xds-server > /dev/null
143 devel@docker ~$ sudo systemctl restart xds-server.service
144 devel@docker ~$ tail -f /tmp/xds-server/logs/xds-server.log
147 ### Install SDK cross-toolchain
149 `xds-server` uses cross-toolchain install into directory pointed by `sdkRootDir`
150 setting (see configuration section below for more details).
151 For now, you need to install manually SDK cross toolchain. There are not embedded
152 into docker image by default because the size of these tarballs is too big.
154 Use provided `install-agl-sdks` script, for example to install SDK for ARM64 and
158 seb@laptop ~$ ssh -p 2222 devel@localhost
160 # Install ARM64 SDK (automatic download)
161 devel@docker ~$ sudo /usr/local/bin/xds-utils/install-agl-sdks.sh --arch aarch64
163 # Install Intel corei7-64 SDK (using an SDK tarball that has been built or downloaded manually)
164 devel@docker ~$ sudo /usr/local/bin/xds-utils/install-agl-sdks.sh --arch corei7-64 --file /tmp/poky-agl-glibc-x86_64-agl-demo-platform-crosssdk-corei7-64-toolchain-
171 `xds-server` serves a web-application at [http://localhost:8000](http://localhost:8000)
172 when XDS server is running on your host. Just replace `localhost` by the host
173 name or ip when XDS server is running on another host. So you can now connect
174 your browser to this url and use what we call the **XDS dashboard**.
177 xdg-open http://localhost:8000
180 Then follow instructions provided by this dashboard, knowing that the first time
181 you need to download and start `xds-agent` on your local machine.
183 To download this tool, just click on download icon in dashboard configuration
184 page or download one of `xds-agent` released tarball: [https://github.com/iotbzh/xds-agent/releases](https://github.com/iotbzh/xds-agent/releases).
186 See also `xds-agent` [README file](https://github.com/iotbzh/xds-agent) for more details.
188 ## Build xds-server from scratch
192 - Install and setup [Go](https://golang.org/doc/install) version 1.7 or
193 higher to compile this tool.
194 - Install [npm](https://www.npmjs.com/)
195 - Install [gulp](http://gulpjs.com/)
200 sudo apt-get install golang npm curl git zip
201 sudo npm install -g gulp-cli
207 sudo zypper install go npm git curl zip
208 sudo npm install -g gulp-cli
211 Don't forget to open new user session after installing the packages.
217 Create a GOPATH variable(must be a full path):
220 export GOPATH=$(realpath ~/workspace_go)
223 Clone this repo into your `$GOPATH/src/github.com/iotbzh` and use delivered Makefile:
226 mkdir -p $GOPATH/src/github.com/iotbzh
227 cd $GOPATH/src/github.com/iotbzh
228 git clone https://github.com/iotbzh/xds-server.git
233 And to install `xds-server` (by default in `/usr/local/bin`):
239 >**NOTE:** Used `DESTDIR` to specify another install directory
241 >make install DESTDIR=$HOME/opt/xds-server
244 #### XDS docker image
246 As an alternative to a pre-build image, you can rebuild the container from scratch.
247 `xds-server` has been integrated as a flavour of AGL SDK docker image.
248 So to rebuild docker image just execute following commands:
251 # Clone docker-worker-generator git repo
252 git clone https://git.automotivelinux.org/AGL/docker-worker-generator
253 # Start build that will create a docker image
254 cd docker-worker-generator
255 make build FLAVOUR=xds
260 `xds-server` configuration is driven by a JSON config file (`config.json`).
262 Here is the logic to determine which `config.json` file will be used:
264 1. from command line option: `--config myConfig.json`
265 1. `$HOME/.xds/config.json` file
266 1. `<current dir>/config.json` file
267 1. `<xds-server executable dir>/config.json` file
269 Supported fields in configuration file are (all fields are optional and example
270 below corresponds to the default values):
272 - **httpPort** : HTTP port of client webapp / dashboard
273 - **webAppDir** : location of client dashboard (default: webapp/dist)
274 - **shareRootDir** : root directory where projects will be copied
275 - **logsDir** : directory to store logs (eg. syncthing output)
276 - **sdkRootDir** : root directory where cross SDKs are installed
277 - **syncthing.binDir** : syncthing binaries directory (default: executable directory)
278 - **syncthing.home"** : syncthing home directory (usually .../syncthing-config)
279 - **syncthing.gui-address** : syncthing gui url (default http://localhost:8384)
280 - **syncthing.gui-apikey** : syncthing api-key to use (default auto-generated)
285 "webAppDir": "webapp/dist",
286 "shareRootDir": "${HOME}/.xds/projects",
287 "logsDir": "/tmp/logs",
288 "sdkRootDir": "/xdt/sdk",
291 "home": "${HOME}/.xds/syncthing-config",
292 "gui-address": "http://localhost:8384",
293 "gui-apikey": "123456789",
298 >**NOTE:** environment variables are supported by using `${MY_VAR}` syntax.
302 ### XDS server architecture
304 The server part is written in *Go* and web app / dashboard (client part) in
309 +-- bin/ where xds-server binary file will be built
311 +-- agent-config.json.in example of config.json file
313 +-- glide.yaml Go package dependency file
315 +-- lib/ sources of server part (Go)
317 +-- main.go main entry point of of Web server (Go)
319 +-- Makefile makefile including
321 +-- README.md this readme
323 +-- scripts/ hold various scripts used for installation or startup
325 +-- tools/ temporary directory to hold development tools (like glide)
327 +-- vendor/ temporary directory to hold Go dependencies packages
329 +-- webapp/ source client dashboard (Angular2 app)
332 Visual Studio Code launcher settings can be found into `.vscode/launch.json`.
336 - replace makefile by build.go to make Windows build support easier
338 - add more documentation
339 - add authentication / login (oauth) + HTTPS
340 - enable syncthing user/password + HTTPS