![using sitesucker with login using sitesucker with login](https://mobirise.com/engine/data/upload/2017/03/mobirise-login-password.jpg)
There are quite a few things going on in this script so let me try and explain the pieces that I have in there: There are an immense number of options but I figure my case should be relatively simple.
#USING SITESUCKER WITH LOGIN MANUAL#
see the immense Manual for more details
![using sitesucker with login using sitesucker with login](https://bavatuesdays.com/wp-content/uploads/2016/12/Screenshot-2016-12-11-16.42.51-1024x534.png)
So ultimately, we cannot host the same codebase on campus for the backups. There is no support for PostgreSQL on campus.The database engine powering the site is PostgreSQL.I did not have access to the servers/services.Media (images, videos, etc) were hosted on an entirely separate server/service.Codebase was not hosted on our servers.There were a few hurdles facing me on this task:
#USING SITESUCKER WITH LOGIN ARCHIVE#
From working on server tuning to writing up small scripts to do batch tasks to small applications for integration with outside services such as google apps, it helps ensure that I don't fry my brain in one area :) I was recently asked to figure out a way to create an archive (on some sort of schedule) of one of our art journals. At my workplace, there are often times when I am *not* working with Drupal (contrary to what people might think ^_^).