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

Update pages/05.community/20.faq/faq.md

Browse source 
Co-authored-by: tituspijean <titus+yunohost@pijean.ovh>
This commit is contained in:
Alexandre Aubin 2023-09-05 13:30:12 +02:00 • committed by GitHub
parent 9874c95493
commit 9c9c869023
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
pages/05.community/20.faq/faq.md
View file

@ -88,7 +88,7 @@ If this does not convince you, there are other projects running on other distrib
People have been tempted to compare YunoHost packages to traditional package managers (such as Debian's `.deb`), which hold a different purpose. Traditional package managers are meant to install low-level purpose of installing files, commands, programs and services on the system. It is often your duty to configure them properly, simply because there is no standard server setup. Typically, web apps requires a lot of configuration because they rely on a web server and a database (and the single sign-on). People have been tempted to compare YunoHost packages to traditional package managers (such as Debian's `.deb`), which hold a different purpose. Traditional package managers are meant to install low-level purpose of installing files, commands, programs and services on the system. It is often your duty to configure them properly, simply because there is no standard server setup. Typically, web apps requires a lot of configuration because they rely on a web server and a database (and the single sign-on).
YunoHost manipulates high-level abstractions (apps, domains, users...) and defines a standard setup (NGINX, Postfix, Metronome, SSOwat...) and, because of this, can handle the configuration for the user. YunoHost manages high-level abstractions (apps, domains, users...) and defines a standard setup (NGINX, Postfix, Metronome, SSOwat...) and, because of this, can handle the configuration for the user.
#### When will [this feature] be implemented? Why isn't [that app] packaged yet? I cannot believe you do not do [this] yet! #### When will [this feature] be implemented? Why isn't [that app] packaged yet? I cannot believe you do not do [this] yet!