Using VM image

About VM Image

Webida Server VM Image is built on Ubuntu 14.04.3 from VirtualBox.

• shell account : webida / webida
• MySQL Root password : webida

You can sudo from webida user.

Most configurations are using default. Quota support is enabled via BTRFS. Read Prerequisites and Installation guide first what's done in the image.

• VM does not support cordova app project
• VM does not support java project
• VM has (usually) very limited I/O bandwidth normally. We don't recommend more than 10 concurrent sessions.

Before configurating your VM

Even though VM is ready, there's no free lunch. Log-in with SSH or virtualbox console with shell account webida, and do configure your VM first.

First of all, stop webida service. $ sudo stop webida and read Configurations guide carefully. You have some tasks before launching service again. Then, configure networking of your VM & webida LXC container. You may have to shut-down or reboot your VM to change networking configurations.

Network configuration

Using virtualbox, you should enable NAT networking via virtual box manager and should set port-forwarding to the VM.

• VM is configured to use 10.0.2.6 IP statically, not via DHCP. Edit /etc/network/interfaces to be suitable with your virtualbox config.
• You may have to edit LXC network configuration for your own NAT network configuration. VM assigns LXC networks to 10.0.3.* - If you want to change the IP range (not to conflict with your 10.x VM networks) change LXC networking configuration first and edit conf.js.
• Enable port-forwarding to VM with virtual box manager. If your VM has IP 10.0.2.6
  • 0.0.0.0:2222 -> 10.0.2.6:22
  • 0.0.0.0:5001 -> 10.0.2.6:5001
  • 0.0.0.0:5002 -> 10.0.2.6:5002
  • 0.0.0.0:5003 -> 10.0.2.6:5003
  • 0.0.0.0:5004 -> 10.0.2.6:5004
  • 0.0.0.0:5008 -> 10.0.2.6:5008
  • 0.0.0.0:5010 -> 10.0.2.6:5010
  • 0.0.0.0:5011 -> 10.0.2.6:5011
  • 0.0.0.0:5090 -> 10.0.2.6:5090
• If you specified some other ports in conf.js, change the port-forwarding configuration, too.

After setting complete, Run '''lxc-start -n webida' and test container can access external networks via git or curl.

Edit conf.js

If you don't know where's conf.js, read Configurations first.

If you have changed LXC network configuration, then edit conf.service.fs.container.lxc.network in conf.js, too. After changing conf.js, always run node conf.js to check. Don't miss to change conf.domain value to your host machine's IP, or some accessbile IP from web browsers. Be sure to stop webida service before editing conf.js I

Fixing oauth client URLS

As mentioned in Configurations guide, you need to change oauth client informations stored in DB.

$ mysql -uwebida -pwebida webida
mysql> update oauth_client recirect_url='http://xxx.yyy.zzz.www:5001/pages/auth.html' where name='app-dashboard'; 
mysql> update oauth_client recirect_url='http://xxx.yyy.zzz.www:5001/-/ide/auth.html' where name='webida-client'; 

If you want to servce https, you may have to change the urls' scheme from http to https, also.

Default user account

log-in with the [email protected] for testing your VM

Running Service

sudo start webida or reboot your VM

Connect to http://your.ip:5001/ with latest chrome or firefox. VM has a pre-created user account, '[email protected]' with password 'webida'

Running services without smtp server

If you want to run service without SMTP service to send sign-up mail, you may have to send activation URL in log file for each user. The activation URL will work with any browser.