Re: [rt-users] Upgrade question
Quoting Kevin Falcone falc...@bestpractical.com: 4.0.17 was actually added to unstable and testing at the end of August. The Debian packager for RT works quite hard. Ah, I did not know that, though I only run stable in a production environment. 2.) Install RT v4.0.17 on new server. Import configs and database from current 4.0.7 server. Jump to the database schema upgrade part of the upgrade instructions This is what I would do. OK, thanks for the confirmation that that is the way to go (don't worry, I won't hold you accountable for anything that goes wrong! lol) -Alan -- RT Training in New York, October 8th and 9th: http://bestpractical.com/training
[rt-users] Upgrade question
Hello, I currently have RT v4.0.7 installed on a Debian server (RT was installed from Debian repositories). For various reasons, I need to put RT onto a new server, and was going to stick with Debian, but instead of using RT from the repositories, I am planning on doing a source install (the repositories are not updated very often, and doing a source install will be easier to keep RT updated, IMO) I am wondering what the best way to go about this is. I am seeing two ways to do this: 1.) Install RT v4.0.7 on the new server, then import current configs and database. Once confirmed all is working properly, perform upgrade to v4.0.17. Or 2.) Install RT v4.0.17 on new server. Import configs and database from current 4.0.7 server. Jump to the database schema upgrade part of the upgrade instructions The second option would of course be easier and more efficient, as it eliminates a step, and it seems to me that it should work, since it seems the biggest part of upgrading RT seems to be the database schema part; I just don;t know if there might be any gotchas doing it that way. What would be the best/recommended way to go? Thanks! :-) -Alan RT Training in New York, October 8th and 9th: http://bestpractical.com/training
Re: [rt-users] Reverse Proxy + RT 4.0.4 + mod_auth_cas on CentOS 6
Quoting Jan Niezbedny janniezbedny1...@gmail.com: fine, but I noticed one interesting thing. I have HTTPS on login page but when I login into RT that changes to HTTP. Without seeing your configuration it is hard to say for sure. One guess is that in the VirtualHost container for the https:// you have it going to the internal server using http:// ?? -Alan We're hiring! http://bestpractical.com/jobs
[rt-users] RTx::AssetTracker problem: Cannot add new asset
Hello, I am running RT3.8 on a Debian Squeeze server. I have installed AssetTracker 2.0.0b2. I am able to create asset types, custom fields, etc., however in the upper right were New Asset of Type should be (so I can add and asset), it shows the code instead of the actual button: LABEL ACCESSKEY=9 SELECT NAME =Type onchange=document.CreateAssetOfType.submit() class=select-queue OPTION VALUE=6 0 Application /OPTION OPTION VALUE=5 0 Components /OPTION OPTION VALUE=1 0 Computers /OPTION OPTION VALUE=2 0 Network /OPTION OPTION VALUE=3 0 Peripherals /OPTION OPTION VALUE=4 0 Storage /OPTION /SELECT /LABEL The above is what displays instead of the button. Any idea what is wrong and how I might fix it? Thanks! :-) -A. We're hiring! http://bestpractical.com/jobs
