YunoHost/ynh-dev
1
0
Fork 0
mirror of https://github.com/YunoHost/ynh-dev.git synced 2024-09-03 20:05:59 +02:00
Code Issues Projects Releases Packages Wiki Activity

More comments on the tradeoff LXC vs Virtualbox, and local vs remote

Browse source
This commit is contained in:
Alexandre Aubin 2019-05-21 16:45:04 +02:00 • committed by Luke Murphy
parent ab36afb151
commit a3e372d5a7
No known key found for this signature in database
GPG key ID: 5E2EF5A63E3718CC
1 changed files with 17 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
README.md
View file

@ -52,18 +52,27 @@ your capacities and resources when aiming to setup a development environment.
Yunohost can be developed on using a combination of the following technologies:
* Git (any version is sufficient)
* Virtualbox (>= 6.x)
* Vagrant (>= 2.x)
* LXC (>= 3.x)
* Vagrant-LXC (>= 1.4.x)
LXC is typically lightweight but you may find the initial setup complex
(in particular network configuration). Alternatively, you may be able
to setup a local environnement using Virtualbox which is kinda more
resource-hungry :
* Virtualbox (>= 6.x)
* Vagrant-virtualbox (>= ?.?.?)
Please keep in mind that these versions may not be available on your OS
distribution and you may be required to install them as binary or from source.
There are no guarantees of stability on newer major versions.
This local development path will not allow you to easily test your email stack
or deal with deploying SSL certificates, for example. A remote machine should
be used for these cases.
This local development path allows to work without an internet connection,
but be aware that it will *not* allow you to easily test your email stack
or deal with deploying SSL certificates, for example, as your machine is
likely to not be exposed on the internet. A remote machine should be used
for these cases.
Depending on your needs, this setup can be very convenient.
@ -76,9 +85,10 @@ Yunohost can be deployed as a typical install on a remote VPS. You can then use
`ynh-dev` to configure a development environment on the server.
This method can potentially be faster than the local development environment
assuming you have familiarity with working on VPS machines. It is also a good
option if the required system dependencies (Vagrant, Virtualbox, etc.) are not
easily available to you on your distribution.
assuming you have familiarity with working on VPS machines, if you always have
internet connectivity when working, and if you're okay with paying a fee. It
is also a good option if the required system dependencies (Vagrant, Virtualbox,
etc.) are not easily available to you on your distribution.
Please be aware that this method should **not** be used for a end-user facing
production environment.