All data is stored in ~/OBSLight and subdirectories.
Configuration file is ~/OBSLight/obslightConfig.
Running the OBS server server appliance on your desktop or laptop via a virtual machine is a common practice during evaluation tests.
The main advantage is that you do not need a special authorisation from your IT department to start playing but you need to allocate at least 2GB to the appliance and as many CPU cores that you can spare.
As a general rule using the bridge mode is advisable. Note this is not the default option of VirtualBox.
The NAT mode is interesting to run an OBS Light server via a VPN or for unconnected demos. In that case you will need to declare NAT rules in your Vitual Machine Manager redirecting the ports 80, 81 and 82 from your local host to your OBS appliance internal NAT address (with VitualBox under Linux rerouting port bellow 1000 is reserved for root only).
Do not forget to add a host name "obslightserver" in your workstation pointing to the OBS Light server appliance IP address or localhost in the case of a NAT configuration.
The kernel package has flags to prevent builds on ARM. To compile an ARM kernel, you must use another package, for example the kernel-adaptation-n900 package.
If the project on your OBS doesn’t provide some dependencies and you must add a repository to your chroot's zypper configuration, you have two choices:
obslight addRepoInChRoot --projectLocalName MeeGo_1.2_oss --url http://download.meego.com/live/MeeGo:/1.2:/non-oss/MeeGo_1.2/ --alias "MeeGo_non-oss"
obslight addRepoInChRoot --projectLocalName MeeGo_1.2_oss --fromProject $ProjectName
Bugs are centralized on MeeGo's bugzilla.