Abstract
This HoTo will show you how to install Wendelin inside your own virtual machine.
Requirements
- A virtual machine running Debian Buster or Debian Stretch, 64bit
- 4 GB of RAM
- At least 20GB of disk space
- Your VM hostname should be "localhost"
Initial setup
Once you have your virtual machine up and running, run (root permissions are needed):
To check up on the status of your build automatically please run:
root@localhost:~# watch -n 30 erp5-show -s
This way if something goes wrong you will be notified immediately. The total time for install and setup should be around less than an hour, however it doesn't need any interaction from user.
When is my Wendelin instance ready?
You can check if your Wendelin instance is ready using:
root@debian:~# erp5-show -s
If your instance is ready the script will printout:
Build successful, connect to:
https://<some_auto_generated_ip>
with
username: zope password: <some_random_password>
Configure Wendelin instance
Wendelin platform is installed using ERP5 Configurator. Here are the configuration instructions:
- Please do get from "erp5-show -s" the IP address of the Wendelin instance then point your browser to it like so https://<some_auto_generated_ip>/erp5 (please note that we intentionally add "erp5" which is Wendelin's root instance url)
- Please login with username and password already provided by "erp5-show -s" script
- From top left select drop down box select 'Configure your Site' and then in next page select Wendelin Configuration.
- Simply follow the instructions and accept defaults suggested for this two page installation. Please note that the configuration phase can last as long as 15-20 minutes.
That's how we install Wendelin. After this you have a basic Wendelin platform.
How to use Wendelin
You can look at code for this examples for inspirations for writing your own ones using the quick link in "My favorites" menu -> "Manage Components".
From the same location you can also run live tests by specifying the test name to: testWendelin or write own code and test it using developer-Forum.Create.Unit.Tests