Jingga/User-Guide
1
0
Fork 0
mirror of https://github.com/Karaka-Management/User-Guide.git synced 2026-01-10 20:08:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

spellchecking

Browse Source
This commit is contained in:
Dennis Eichhorn 2021-03-07 21:37:52 +01:00
parent 327a87ee39
commit 52e90b2c54
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
administration/jobs.md
View File

@ -2,7 +2,7 @@
Depending on the server environment it's possible to setup automated jobs/tasks that run at a specific time or interval. This can be useful for automatic updates, backups etc. The application provides a list of default jobs that it can setup. Other modules may provide additional jobs which can also be monitored in the jobs overview.
Simple web servers usually don't allow to register automated jobs. For this purpose jobs can get registered on our own servers which then in return call your application through an api interface. While this enables the use of automated jobs/tasks in situations where this usually wouldn't be possible also is highly dependent on a stable internet connection and server. If possible the local registration of jobs is always preferred.
Simple web servers usually don't allow to register automated jobs. For this purpose jobs can get registered on our own servers which then in return call your application through an API interface. While this enables the use of automated jobs/tasks in situations where this usually wouldn't be possible also is highly dependent on a stable Internet connection and server. If possible the local registration of jobs is always preferred.
Jobs don't have to be used they simply provide a convenient way to automate certain tasks that otherwise have to be performed manually.

4
security/server.md
View File

@ -1,6 +1,6 @@
# Server Security
Since server security or operating system security is a very large topic this chapter only provides a rough schematic of some best practices which you should look up on the internet. These are the most common practices and are well documented in many online documentations for multiple operating systems. While these practices and guidelines are the basics for most server administrators they may seem to be confusing or unnecessary for people that have never managed their own server. If you are only using standard webhosting with a simple ftp upload and database system and no ssh or vnc login (vps, root server etc.) the following guidelines don't apply since this should have been already done by any responsible webhost provider.
Since server security or operating system security is a very large topic this chapter only provides a rough schematic of some best practices which you should look up on the Internet. These are the most common practices and are well documented in many online documentations for multiple operating systems. While these practices and guidelines are the basics for most server administrators they may seem to be confusing or unnecessary for people that have never managed their own server. If you are only using standard web hosting with a simple FTP upload and database system and no ssh or VNC login (VPS, root server etc.) the following guidelines don't apply since this should have been already done by any responsible web host provider.
## Access Restrictions
@ -8,7 +8,7 @@ In general only whitelist user access permissions instead of blacklisting them.
## HTTPS
HTTPS is a protocol or form of encrypted communication between client and server. It prevents attackers from reading the data being sent back and forth between server and client, which can be very critical when we are talking about user, company, customer, employee, private information. Nowadays it's fairly simple and cheap to setup and a must have for every website and application that is accessible through the internet browser. It is recommended to use the free service of Let's encrypt. Since https is a matter of server configuration this cannot be achieved by the application itself. Follow the step-by-step instructions of https://certbot.eff.org/ in order to setup https for your own server. Normal webhosting services usually optionally offer https for a premium which you should definitely consider. While you'll most likely have to pay your webhosting agency they will do the setup for you. Just remember that the actual certificate can be obtained for free and while services may try to sell you more expensive certificates they are essentially the same as the free alternative.
HTTPS is a protocol or form of encrypted communication between client and server. It prevents attackers from reading the data being sent back and forth between server and client, which can be very critical when we are talking about user, company, customer, employee, private information. Nowadays it's fairly simple and cheap to setup and a must have for every website and application that is accessible through the Internet browser. It is recommended to use the free service of Let's encrypt. Since https is a matter of server configuration this cannot be achieved by the application itself. Follow the step-by-step instructions of https://certbot.eff.org/ in order to setup https for your own server. Normal web hosting services usually optionally offer https for a premium which you should definitely consider. While you'll most likely have to pay your web hosting agency they will do the setup for you. Just remember that the actual certificate can be obtained for free and while services may try to sell you more expensive certificates they are essentially the same as the free alternative.
## Root Login