Having downloaded and installed both products we ignore the normal usage of VirtualBox remember that Vagrant is your Virtual Machine Manager so although we need VirtualBox installed we do not need to open or use their interface. We will use VirtualBox and Vagrant on MacOS. Typically, this would be VirtualBox as it it free on all platforms. In simple terms Vagrant is a Virtual Machine Manager and requires a Virtualization Engine. We start by looking at provisioning Vagrant Virtual Machines with Ansible, but just Vagrant to start. Provisioning Virtual Machines Using Vagrant Alone Using Ansible 2.10.x installed on MacOS I will demonstrate how you can use Vagrant and Ansible in collaboration. The Ansible controller can be installed on Linux and MacOS, so if your Vagrant host is one of those operating systems, you are ready to both deploy your Virtual Machine with Vagrant and provision it with your Ansible Playbooks. The great thing with Vagrant is that you can further configure your Virtual Machine using Provisioners, one of those provisioners is Ansible. Vagrant is free to use and install on Linux, Windows and MacOS. Within you own environment you may well be used to using Vagrant from HashiCorp to deploy Virtual Machines. The Freeciv web client is a volunteer non-profit effort.Provisioning Virtual Machines Using Vagrant and Ansible is a lot easier than you think especially if you already have some Ansile experience. It is quite quick to setup a Vagrant image if you follow the description found on the Github page. I would be happy to help anyone setup a development environment. > I would be especially interested in the client-side code which is readable but, on first sight, a bit overwhelming for something one would do after a regular day job. There is a TODO-file, but the main issue tracker is on gna.org here: Or is there a mailing list/irc channel which gets used for coordination? > Because any issue tracker would make it easier to discuss the details of the task at hand. There are also plans for a WebGL version, but that would take much more work. As for future plans, I hope to continue improving the game and making it work on more mobile devices. However, the code-bases are still separate, so the Freeciv web client is maintained in Github, and has code in Javascript, Java, Python and C, while the Freeciv project is mainly implemented in C and is still hosted in SVN on gna.org. Today the Freeciv web client is a part of the Freeciv project. The Freeciv web client started as a fork of the Freeciv project in about 2007, at the time called. > Maybe someone from the team could say a few words about the projects organisation, plans and communications. API docs and/or (more?) unit tests would be awesome because I think one of the benefits of freeciv-web is be that some of it is/could be easy to customize for advanced players. I would be especially interested in the client-side code which is readable but, on first sight, a bit overwhelming for something one would do after a regular day job. Is that a conscious decision? Because any issue tracker would make it easier to discuss the details of the task at hand. I know there's a github repo, but you seem to use a TODO file instead of the issue tracker and/or wiki. Maybe someone from the team could say a few words about the projects organisation, plans and communications. As a civ fanatic I thought often about contributing, but never started to do it. Thank you! The Freeciv web client is one of my favorite projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |