we have a Turnkey Tomcat installation using basic config i.e. / = localhost
we need to add a virtual host, such that new hostname 'new.newdomain.com' points to
existing webapp located at /newdomain (in webapps list)
this is a 2 line change in Apache httpd.conf but the virtual hosts manager cannot be made to work correctly and we do not know what we are doing wrong. Help??
I setup a LAMP instance with daily backups. Yesterday I installed some PEAR modules and then decided I didnt really want them. I did a restore to a version before PEAR was installed and to my suprise the module still fired up on the next reboot. Is this user error on my part(I assume) or is there some design reason as to why this module was survive the restore?
Details -
After deciding to rollback I went to TURNKEY HUB found the backup from the day before. (At the time it was the last backup) so I ran this command line.
I just build a LAPP Turnkey appliance and tried to back it up to my turnkeylinux backups. I intitialized the backup with tklbam-init using my API key and that succeeded. Then, I issued the "tklbam-backup" command and the following appeared:
We have an installation at work of vTiger 5.2.2 that we are running on a non-TKL platform because you guys didn't have it in TKL when we started to use it. The database has grown, as has the number of users, and we are seriously considering going to an on-demand platform rather than self-hosting it. vTiger also just released a new version (5.3RC) that will be frozen in 2-3 weeks. This is putting the impetus on us now to upgrade and decide on a long-term solution at the same time.
OK so I've got a configured Turnkey machine image I used to demo to a customer. Now the customer wants to go live with it but move it or copy it rather under their own AWS account login.
OK so I've got a configured Turnkey machine image I used to demo to a customer. Now the customer wants to go live with it but move it or copy it rather under their own AWS account login.