You’ll find hereafter how the Ubuntu server was prepared for this article. Finally we’ll see how we can analyze these logs on a Windows workstation. We’ll then see how to add useful additional fields and how to share the log files to be easily downloadable and synchronized from a remote workstation. We’ll see in this article how to configure the Apache access logs to facilitate archiving and synchronization of the log files. The article is based on an Ubuntu installation on which a web site is running. It’s now time to see how to monitor the web site activity on an Apache web server running on Linux. I have learned, that keeping source code and configuration data in the same repo makes sometime situation more dificult (that is why I am working on using salt).All my previous articles were about how to configure HTTP logs in IIS. Salt (saltstack) could serve too, but requires a bit more learning and setup).
Rsync seems in many cases serve well enough or better (be aware of files being created at app runtime and by files in your app, which shall be removed during ongoing versions and shall be removed on server too).
Personally I would use "one shot ssh" (you asked not to use ssh, but I assume you are asking for "simpler" solution, so one shot call shall work simpler then using ftp, scp or other magic.įrom your devel machine (assuming you have ssh access there): $ ssh "cd /var/ In case, your app needs restart afte an update, then you have to ensure, the restart would happen (this shall be possible using git log command, which will show new line after the update, or you may check, if status code would tell you. One being a cron task, which would regularly call $ git pull
Go to /var/www and clone form bitucket: $ cd /var/wwwĪnd you shall have your directory ready. Generally, you create the project on Bitbucket, find the url of it and then from your devel repo call: $ git remote add origin Prepare repo on develĭevelop and test the app on your devel server.Į.g.
"asking" prod server to pull the updates can be managed by cron (then you have to wait a moment) or you may use other means like one shot call of ssh asking to do git pull and possibly restart your app. Then you commit things from devel to central and as soon as you want to deploy on prod, than you ask prod to pull data from prod.
0 kommentar(er)
