ruj. 02

Deploying a Ruby on Rails application – Passenger

Please edit your Apache configuration file, and add these lines:

LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/ext/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15
PassengerRuby /usr/bin/ruby

After you restart Apache, you are ready to deploy any number of Ruby on Rails applications on Apache, without any further Ruby on Rails-specific configuration! ——————————————– Deploying a Ruby on Rails application: an example Suppose you have a Rails application in /somewhere. Add a virtual host to your Apache configuration file and set its DocumentRoot to /somewhere/public:

<VirtualHost *:80>
 ServerName www.yourhost.com
 DocumentRoot /somewhere/public    # <-- be sure to point to 'public'!
 <Directory /somewhere/public>
  AllowOverride all              # <-- relax Apache security settings
  Options -MultiViews            # <-- MultiViews must be turned off
 </Directory>
</VirtualHost>

And that’s it! You may also want to check the Users Guide for security and optimization tips, troubleshooting and other useful information: /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/doc/Users guide Apache.html Enjoy Phusion Passenger, a product of Phusion (www.phusion.nl) 🙂 http://www.modrails.com/ Phusion Passenger is a trademark of Hongli Lai & Ninh Bui.

Nastavi čitanje

velj. 14

cPanel i WHM log datoteke

General:

Quote:

cPanel/WHM Initial Installation Errors: Location : /var/log/cpanel*install* Description : These log files contain cPanel installation logs & should be referenced first for any issues resulting from new cPanel installations..

Quote:

Cpanel/WHM Service Status Logs: Location : /var/log/chkservd.log Description :The service monitoring demon (chkservd) logs all service checks here. Failed service are represented with a [-] and active services are represented by [+].

Quote:

Cpanel/WHM Accounting Logs: Location : /var/cpanel/accounting.log Description : Contains a list of accounting functions performed through WHM, including account removal and creation..

cPanel/WHM Specific Requests and Errors:

Quote:

cPanel error logs: Location : /usr/local/cpanel/logs/error_log Description : cPanel logs any error it incurs here. This should be checked when you encounter errors or strange behavior in cPanel/WHM…

Quote:

cPanel License Error Logs: Location : /usr/local/cpanel/logs/license_log Description : All license update attempts are logged here. If you run into any errors related to license when logging in, check here.

Quote:

Stats Daemon Logs: Location : /usr/local/cpanel/logs/stats_log Description : The stats daemon (cpanellogd) logs the output from all stats generators (Awstats, Webalizer, Analog) here.

Quote:

Client Information, Requested URL Logs: Location : /usr/local/cpanel/logs/access_log Description : General information related to access cPanel requests is logged here.

Quote:

cPanel/WHM Update Logs: Location : /var/cpanel/updatelogs/update-[TIMESTAMP].log Description : Contains all output from each cPanel update [upcp]. It’s named with the timestamp at which the upcp process was initiated..

Quote:

Bandwidth Logs: Location : /var/cpanel/bandwidth Description : Files contain a list of the bandwidth history for each account. Each named after their respective user.

Quote:

Tailwatchd [New]: Location : /usr/local/cpanel/logs/tailwatchd_log Description : Logs for daemon configuired under tailwatchd ie. cPBandwd, Eximstats, Antirelayd.

Apache Logs:

Quote:

General Error and Auditing Logs: Location : /usr/local/apache/logs/error_log Description : All exceptions caught by httpd along with standard error output from CGI applications are logged here.. The first place you should look when httpd crashes or you incur errors when accessing website.

Quote:

Apache SuExec Logs: Location : /usr/local/apache/logs/suexec_log Description : Auditing information reported by suexec each time a CGI application is executed. Useful for debugging internal server errors, with no relevant information being reported to the Apache error_log, check here for potential suexec policy violations…

Quote:

Domain Access Logs: Location : /usr/local/apache/domlogs/domain.com Description : General access log file for each domain configured with cPanel.

Quote:

Apache Access Logs: Location : /usr/local/apache/logs/access_log Description : Complete web server access log records all requests processed by the server.

Exim :

Quote:

Message Reception and Delivery: Location : /var/log/exim_mainlog or /var/log/exim/mainlog Description : Receives an entry every time a message is received or delivered.

Quote:

Exim ACLs/Policies based RejectLog : Location : /var/log/exim_rejectlog Description : An entry is written to this log every time a message is rejected based on either ACLs or other policies eg: aliases configured to :fail

Quote:

Unexpected or Fatal Errors: Location : /var/log/exim_paniclog Description : Logs any entries exim doesn’t know how to handle. It’s generally a really bad thing when log entries are being written here, and they should be properly investigated..

Quote:

IMAP/POP/SpamAssassin General Logging and Errors: Location : /var/log/maillog & /var/log/messages Description : The IMAP, POP, and SpamAssassin services all log here. This includes all general logging information (login attempts, transactions, spam scoring), along with fatal errors.

FTP:

Quote:

FTP Logins and General Errors: Location : /var/log/messages Description : General information and login attempts are logged here..

Quote:

FTP Transactions logging: Location : /var/log/xferlog or /var/log/messages Description : Is a symbolic link in most cases to /usr/local/apache/domlogs/ftpxferlog, which contains a history of the transactions made by FTP users…

MySQL:

Quote:

MySQL General Information and Errors : Location : /var/lib/mysql/$(hostname).err Description : This path could vary, but is generally located in /var/lib/mysql. Could also be located at /var/log/mysqld.log

Security:

Quote:

Authentication attempts: Location : /var/log/secure Description : Logs all daemons which requires PAM Authentication.

Quote:

Tracking all Bad Logins and Logouts: Location : /var/log/btmp Description : Log of all attempted bad logins to the system. Accessed via the lastb command..

Quote:

Tracking all Logins and Logouts: Location : /var/log/wtmp Description : The wtmp file records all logins and logouts.

Quote:

Last Logins: Location : /var/log/lastlog Description : Database times of previous user logins. The lastlog file is a database which contains info on the last login of each user.

Quote:

WebDav or WebDisk Log : Location : /usr/local/cpanel/logs/cpdavd_error_log Description : The cpdavd daemon is “WebDav” (better known as “WebDisk”) which was introduced in cPanel 11 to allow users to mount their home directory on their personal computer, always having access to the files and content…

Quote:

Cphulkd Logs: Location : /usr/local/cpanel/logs/cphulkd_errors.log Description : cPHulk Brute Force Protection prevents malicious forces from trying to access your server’s services by guessing the login password for that service…. It blacklists IPs that it thinks are trying to run a brute force attack.

Quote:

Failure Logging: Location : /var/log/faillog Description : Faillog formats the contents of the failure log from /var/log/faillog database. It also can be used for maintains failure counters and limits. Run faillog without arguments display only list of user faillog records who have ever had a login failure.

Quote:

Startup/Boot, Kernel & Hardware error messages : Location : /var/log/dmesg Description : dmesg is a “window” into the kernels ring-buffer. It’s a message buffer of the kernel. The content of this file is referred to by the dmesg command. It shows bootlog and the hardware errors..

Tomcat:

Quote:

General Startup, Shutdown & Error Logs: Location : /usr/local/jakarta/tomcat/logs/catalina.err and /usr/local/jakarta/tomcat/logs/catalina.out Description : Logs for Tomcat and all tomcat based applications…

Nastavi čitanje

pro. 26

Postavljanje php.ini postavki za cijeli hosting račun

Nakon podešavanja php.ini datoteke u root direktoriju hosting računa potrebno je u .htaccess datoteci dodati putanju do vlastite php.ini datoteke.
Podešene php postavke vrijediti će za sve .php datoteke na hosting računu, bez obzira da li se nalaze direktno u “/public_html” direktoriju ili nekom drugom poddirektoriju unutar “/public_html” direktorija.
Ukoliko se unutar .htaccess datoteke ne upiše adresa do vlastite php.ini datoteke, vlastite php postavke vrijede samo za php datoteke koje se nalaze u istom direktoriju gdje se nalazi i php.ini datoteka.

U .htaccess datoteci upišite sljedeće, “username” zamijenite sa odgovarajućim imenom hosting računa:

<IfModule mod_suphp.c>
suPHP_ConfigPath /home/username
</IfModule>

U php.ini datoteci podesite vlastite PHP postavke:

allow_url_fopen = On
upload_max_filesize = 20M
post_max_size = 20M 
memory_limit = 256M 
upload_tmp_dir = 80M 
max_execution_time = 600

ili jednostavno prekopirajte sistemsku /usr/local/lib/php.ini datoteku i u njoj obavite potrebne izmjene.

Napomena, ovaj način postavljanja php.ini postavki vrijedi samo kada je PHP podešen kao Apache “suPHP” modul.

Nastavi čitanje

stu. 18

Rekurzivno kopiranje datoteka

Rekuzivno kopiranje svih “index.*” datoteka iz jednog stabla direktorija u drugo stablo direktorija:


rsync -avm --include='index.*' -f 'hide,! */' /izvorni-dir/ /odredišni-dir

Objašnjenje -f ‘hide,! */’: ‘-f‘ znači da rsync filtrira prema predlošku: ‘*/‘ predložak koji označava “bilo koji direktorij” ‘! */‘ označava bilo što što nije direktorij (npr. datoteka) ‘hide,! */‘ znači sakrij sve datoteke i sve direktorije Filtriranje se primjenjuje u redosljedu u kojem je napisano i prvo pravilo koje je zadovoljeno se primjenjuje. –include=’index.*’ ima prednost, što znači da je datoteka uključena u kopiranje ako joj je naziv “index” i završava sa bilo koji tekstom (html, php i sl.) Sve ostale datoteke su isključene iz kopiranja.

Nastavi čitanje