Difference between revisions of "Talk:Remi-safe"
From SME Server
Jump to navigationJump to searchUnnilennium (talk | contribs) (Created page with "usually we set external repo as visible no and status disabled by default, while no rule is written on this. For this particular repo, best practice would be to set it as Vis...") |
Unnilennium (talk | contribs) |
||
| Line 3: | Line 3: | ||
For this particular repo, best practice would be to set it as Visible yes and status enabled. | For this particular repo, best practice would be to set it as Visible yes and status enabled. | ||
The reason behind are : | The reason behind are : | ||
| + | |||
- the repo is designed to NOT conflict with base repo and packages | - the repo is designed to NOT conflict with base repo and packages | ||
| − | - fast update of php package is important for security reason. | + | |
| + | - fast update of php package is important for security reason. Having this repo enabled will help maintaining SME servers secure. | ||
| + | |||
| + | [[User:Unnilennium|Unnilennium]] ([[User talk:Unnilennium|talk]]) 20:08, 12 October 2017 (CEST) | ||
Latest revision as of 19:08, 12 October 2017
usually we set external repo as visible no and status disabled by default, while no rule is written on this.
For this particular repo, best practice would be to set it as Visible yes and status enabled. The reason behind are :
- the repo is designed to NOT conflict with base repo and packages
- fast update of php package is important for security reason. Having this repo enabled will help maintaining SME servers secure.
Unnilennium (talk) 20:08, 12 October 2017 (CEST)
