Fincer
/
linux-server-setup
mirror of https://github.com/Fincer/linux-server-setup
1
0
Fork 0
Code Issues 0 Projects 0 Releases 0 Wiki Activity
Instructions to set up a basic LAMP+SSH server environment
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
84 Commits
1 Branch
4.9 MiB
 
 
Tree: d8b8e59f5b
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'd8b8e59f5b'
${ noResults }
 ZIP  TAR.GZ
Pekka Helenius d8b8e59f5b
iptables.rules: Add note about bruteforce rules 		6 years ago
exercises H5: Update iptables section 6 years ago
images Initial commit 6 years ago
other iptables.rules: Add note about bruteforce rules 6 years ago
patches Update notes of 'patch_apache_break_http_code_standard.patch' 6 years ago
scripts Initial commit 6 years ago
README.md linux_server_setup -> linux-server-setup 6 years ago

README.md

Administration of Linux server/client environment

  • This repository is related to single-server/client Linux (server) environments.

  • This repository, as for now, doesn't contain any advanced set-up & maintenance instructions for multi-client/server environment techniques such as Puppet or SaltStack. For setting up a SaltStack environment, see:

  • This repository doesn't contain instructions to set up containers, such as Docker or systemd-nspawn.

  • The repository is mainly set up as a requirement by a school cource in Haaga-Helia University of Applied Sciences, Helsinki, Finland.

  • The repository contains various exercises, originally presented in Finnish but translated into English due to practical purposes.

  • All bourne shell files (sh) presented in this repository may not be directly related to the exercises but they are useful in some situations.

  • NOTE! Instructions in this repository may not directly apply to your setting. The instructions have not been tested in a production environment, so if you decided to use them in your system configuration, you should apply them with care. I do not take any responsibility in a case of failure or broken system configurations.

Table of contents