Report of Ryzom Forge's meeting - monday, 30th of april 2015.
Tutorials about the base system : Datashhets and Primitives
YannK continue working on tutorials about the base system (meaning Datasheets and Primitives). He has posted recently on how the shops are created and managed in the Primitives. It is on the Khaganat wiki for now, because it was already hard enough for him to manage one wiki system.
Lyne translated it in English so it's ready for transfer on RF wiki as soon as someone knows how to do it.
For the ones who want to help with export: http://khaganat.net/tools/docu-export.php. You'll need to re-read, but it translates most of the dokuwiki tags into mediawiki (for page layout).
Pets
YannK is been working for some time on the pets (so the datasheets) and thinks it will be his next tutorial. It will be the chance to add mobs who follow us and who're not mektoubs.
The idea is to fill all the parameters, so that someone can create the datasheets a "simple" way afterwards.
YannK has never managed anything on the Ryzom Core wiki, but if someone want to transfer them there, he'll appreciate it.
Test server for Ryzom Forge
Mati continue working on how to install a test server for Ryzom Forge.
<Madi> Fist I spent hours to set up a server, recompile the services, set up the web apps... Then I had a problem, the server being on line, I decided to re-do a setup on VM at home for test to avoid making experiments on a server connected 24h a day on the net. And there, again, hours to compile, install... It's when I thought I was going the wrong way.
So I rewrote clearly the objectives:
-make available a test server for ryzom,
-allow everyone to have also at his disposal a test server to make his own tests.
This last point is important, YannK will be able to tell you more about it, he has at his disposal a test VM and it helped himd in this graphical objects tries
My error: I had a dev approach, spent hours setting up a machine by hand, lost again hours for a new machine just after.
How will the basic user do, he who just want to make a test but doesn't have the knowledge to re-edit a scenario of several hours to set up a server?
So I looked on a new paradigm in computer science which takes care of this problem. DevOps. These are tools which allow to automate the set up and installation of a server. First tools like Puppet / Chef / Ansible.
I chose Ansible, because it's the most approachable one to start.
So step 1: I've implemented a script which automate the set up for compiling a ryzom server. Now I can use it on a real server, or on a VM.
On the VM subject, I've used a second tool from the "DevOps" toolkit. It is "vagrant".. It allows with 3 command lignes, to create a VM and to start an ansible script for example on it to "set up" (it is called provisionning) a server. It works on Mac OSX, Windows, Linux.
I've also added to the whole a "Packer" script which allows to create also images of VM for vagrant (kvm, or virtuelbox).
So at this time of my testings: I've got a way to automate the set-up of a real server for Ryzomcome (compile actually) and I can also deploy it automatically on a VM at home.
But at this time, I realise that I've only postponed a problem: If I furnish automatically a ryzomcore server, it takes on a VM on my machine... 8h.
*Madi counts on his finger: take the sources, installe the tools, compile the server, etc... Even if it's automatic, it's easily reached by an average user.
That's when I understand my second error:
The idea of Ansible/Vagrant/packer is to automate the deployment of a server. It should take, say, 15 min... not a whole day.
The problem comes from compiling the sources. There no exist binary packpages for this server.
So I contacted Kervala, and I discussed with him on binary packets which affect the game client. We discussed, and we arrived to the conclusion that we need also binary packets for the server.
At this time, deploying a server, it's just 15 min, binaries to install, a set up script to execute.
As a conclusion: So I created a deposit for the debian/ubuntu binaries through the bintray site. I still have to provide all the scripts which I spoke about here: Patch the install for the binaries packets, ansible scripts, vagrant, packer. I'll try to make it shortly on github/bitbucker because the help of everyone is welcome.
Tutorials about the base system : Datashhets and Primitives
YannK continue working on tutorials about the base system (meaning Datasheets and Primitives). He has posted recently on how the shops are created and managed in the Primitives. It is on the Khaganat wiki for now, because it was already hard enough for him to manage one wiki system.
Lyne translated it in English so it's ready for transfer on RF wiki as soon as someone knows how to do it.
For the ones who want to help with export: http://khaganat.net/tools/docu-export.php. You'll need to re-read, but it translates most of the dokuwiki tags into mediawiki (for page layout).
Pets
YannK is been working for some time on the pets (so the datasheets) and thinks it will be his next tutorial. It will be the chance to add mobs who follow us and who're not mektoubs.
The idea is to fill all the parameters, so that someone can create the datasheets a "simple" way afterwards.
YannK has never managed anything on the Ryzom Core wiki, but if someone want to transfer them there, he'll appreciate it.
Test server for Ryzom Forge
Mati continue working on how to install a test server for Ryzom Forge.
<Madi> Fist I spent hours to set up a server, recompile the services, set up the web apps... Then I had a problem, the server being on line, I decided to re-do a setup on VM at home for test to avoid making experiments on a server connected 24h a day on the net. And there, again, hours to compile, install... It's when I thought I was going the wrong way.
So I rewrote clearly the objectives:
-make available a test server for ryzom,
-allow everyone to have also at his disposal a test server to make his own tests.
This last point is important, YannK will be able to tell you more about it, he has at his disposal a test VM and it helped himd in this graphical objects tries
My error: I had a dev approach, spent hours setting up a machine by hand, lost again hours for a new machine just after.
How will the basic user do, he who just want to make a test but doesn't have the knowledge to re-edit a scenario of several hours to set up a server?
So I looked on a new paradigm in computer science which takes care of this problem. DevOps. These are tools which allow to automate the set up and installation of a server. First tools like Puppet / Chef / Ansible.
I chose Ansible, because it's the most approachable one to start.
So step 1: I've implemented a script which automate the set up for compiling a ryzom server. Now I can use it on a real server, or on a VM.
On the VM subject, I've used a second tool from the "DevOps" toolkit. It is "vagrant".. It allows with 3 command lignes, to create a VM and to start an ansible script for example on it to "set up" (it is called provisionning) a server. It works on Mac OSX, Windows, Linux.
I've also added to the whole a "Packer" script which allows to create also images of VM for vagrant (kvm, or virtuelbox).
So at this time of my testings: I've got a way to automate the set-up of a real server for Ryzomcome (compile actually) and I can also deploy it automatically on a VM at home.
But at this time, I realise that I've only postponed a problem: If I furnish automatically a ryzomcore server, it takes on a VM on my machine... 8h.
*Madi counts on his finger: take the sources, installe the tools, compile the server, etc... Even if it's automatic, it's easily reached by an average user.
That's when I understand my second error:
The idea of Ansible/Vagrant/packer is to automate the deployment of a server. It should take, say, 15 min... not a whole day.
The problem comes from compiling the sources. There no exist binary packpages for this server.
So I contacted Kervala, and I discussed with him on binary packets which affect the game client. We discussed, and we arrived to the conclusion that we need also binary packets for the server.
At this time, deploying a server, it's just 15 min, binaries to install, a set up script to execute.
As a conclusion: So I created a deposit for the debian/ubuntu binaries through the bintray site. I still have to provide all the scripts which I spoke about here: Patch the install for the binaries packets, ansible scripts, vagrant, packer. I'll try to make it shortly on github/bitbucker because the help of everyone is welcome.