Friendica Communications Platform (please note that this is a clone of the repository at github, issues are handled there) https://friendi.ca
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

58 lines
2.4 KiB

7 years ago
  1. Vagrant for Friendica Developers
  2. ===================
  3. * [Home](help)
  4. Getting started
  5. ---------------
  6. [Vagrant](https://www.vagrantup.com/) is a virtualization solution for developers.
  7. No need to setup up a webserver, database etc. before actually starting.
  8. Vagrant creates a virtual machine for you that you can just run inside VirtualBox and start to work directly on Friendica.
  9. It brings an Ubuntu Xenial (16.04) with PHP 7.0 and MySQL 5.7.16
  10. What you need to do:
  11. 1. Install VirtualBox and vagrant.
  12. Please use an up-to-date vagrant version from https://www.vagrantup.com/downloads.html.
  13. 2. Git clone your Friendica repository.
  14. Inside, you'll find a "Vagrantfile" and some scripts in the utils folder.
  15. 3. Run "vagrant up" from inside the friendica clone:
  16. $> vagrant up
  17. Be patient: When it runs for the first time, it downloads an Ubuntu Server image.
  18. 4. Run "vagrant ssh" to log into the virtual machine to log in to the VM:
  19. $> vagrant ssh
  20. 5. Open you test installation in a browser.
  21. Go to 192.168.22.10.
  22. The mysql database is called "friendica", the mysql user and password both are "friendica".
  23. 6. Work on Friendica's code in your git clone on your machine (not in the VM).
  24. Your local working directory is set up as a shared directory with the VM (/vagrant).
  25. 7. Check the changes in your browser in the VM.
  26. Debug via the "vagrant ssh" login.
  27. Find the Friendica log file /vagrant/logfile.out.
  28. 8. Commit and push your changes directly back to Github.
  29. If you want to stop vagrant after finishing your work, run the following command
  30. $> vagrant halt
  31. in the development directory.
  32. This will not delete the virtual machine.
  33. 9. To ultimately delete the virtual machine run
  34. $> vagrant destroy
  35. $> rm /vagrant/config/local.config.php
  36. to make sure that you can start from scratch with another "vagrant up".
  37. The vagrant Friendica instance contains a test database.
  38. You will then have the following accounts to login:
  39. * admin, password admin
  40. * friendica1, password friendica1
  41. * friendica2, password friendica2 and so on until friendica5
  42. * friendica1 is connected to all others. friendica1 has two groups: group1 with friendica2 and friendica4, group2 with friendica3 and friendica5.
  43. * friendica2 and friendica3 are connected. friendica4 and friendica5 are connected.
  44. For further documentation of vagrant, please see [the vagrant*docs*](https://docs.vagrantup.com/v2/).