mirror of
https://github.com/YunoHost/yunohost.git
synced 2024-09-03 20:06:10 +02:00
Wordin
This commit is contained in:
parent
07e5ead038
commit
31c8b88f44
1 changed files with 8 additions and 8 deletions
|
@ -294,14 +294,14 @@
|
||||||
"migration_0005_not_enough_space": "Not enough space is available in {path} to run the migration right now :(.",
|
"migration_0005_not_enough_space": "Not enough space is available in {path} to run the migration right now :(.",
|
||||||
"migration_0006_disclaimer": "Yunohost now expects admin and root passwords to be synchronized. By running this migration, your root password is going to be replaced by the admin password.",
|
"migration_0006_disclaimer": "Yunohost now expects admin and root passwords to be synchronized. By running this migration, your root password is going to be replaced by the admin password.",
|
||||||
"migration_0006_done": "Your root password have been replaced by your admin password.",
|
"migration_0006_done": "Your root password have been replaced by your admin password.",
|
||||||
"migration_0006_cancelled": "YunoHost has failed to improve the way your ssh conf is managed.",
|
"migration_0006_cancelled": "YunoHost has failed to improve the way your SSH conf is managed.",
|
||||||
"migration_0006_cannot_restart": "SSH can't be restarted after we tried to cancel the migration 6.",
|
"migration_0006_cannot_restart": "SSH can't be restarted after trying to cancel migration number 6.",
|
||||||
"migration_0007_general_warning": "To ensure a global security of your server, YunoHost recommends to let it manage the SSH configuration of your server. Your current SSH configuration differs from common default configuration. If you let YunoHost reconfigure it, the way to access with SSH to your server could change after this migration:",
|
"migration_0007_general_warning": "To improve the security of your server, it is recommended to let YunoHost manage the SSH configuration. Your current SSH configuration differs from the recommended configuration. If you let YunoHost reconfigure it, the way you connect to your server through SSH will change in the following way:",
|
||||||
"migration_0007_port": "- you will have to connect using port 22 instead of your custom SSH port. Feel free to reconfigure it",
|
"migration_0007_port": " - you will have to connect using port 22 instead of your current custom SSH port. Feel free to reconfigure it ;",
|
||||||
"migration_0007_root": "- you will not be able to connect with root user, instead you will have to use admin user.",
|
"migration_0007_root": " - you will not be able to connect with root user, instead you will have to use the admin user ;",
|
||||||
"migration_0007_dsa": "- you might need to invalidate a warning and to recheck fingerprint of your server, because DSA key will be disabled.",
|
"migration_0007_dsa": " - you might need to invalidate a warning and to recheck the fingerprint of your server, because DSA key will be disabled ;",
|
||||||
"migration_0007_risk": "If you agree to let YunoHost replace your configuration and change the way to access your server, make the migration else skip it.",
|
"migration_0007_risk": "If you understand those warnings and agree to let YunoHost override your current configuration, run the migration. Otherwise, you can also skip the migration though it is not recommended.",
|
||||||
"migration_0007_no_risk": "No major change in the way has been found, but it's difficult to be sure. If you agree to let YunoHost replace your configuration and change the way to access your server, make the migration else skip it.",
|
"migration_0007_no_risk": "No major risk has been indentified about overriding your SSH configuration - but it's difficult to be sure. If you agree to let YunoHost override your current configuration, run the migration. Otherwise, you can also skip the migration though it is not recommended.",
|
||||||
"migrations_backward": "Migrating backward.",
|
"migrations_backward": "Migrating backward.",
|
||||||
"migrations_bad_value_for_target": "Invalid number for target argument, available migrations numbers are 0 or {}",
|
"migrations_bad_value_for_target": "Invalid number for target argument, available migrations numbers are 0 or {}",
|
||||||
"migrations_cant_reach_migration_file": "Can't access migrations files at path %s",
|
"migrations_cant_reach_migration_file": "Can't access migrations files at path %s",
|
||||||
|
|
Loading…
Add table
Reference in a new issue