-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get RT running in a container #1
Comments
Ask had been working on a version here: https://github.com/abh/rt-docker RT has cronjobs that need to be scheduled, so that's one consideration when setting it up with docker. It also expects a local mail agent so it can call "sendmail" for sending email. Incoming email gets into RT via REST, so rt-mailgate can run elsewhere if it's easier to set up separately. RT can run with nginx: https://docs.bestpractical.com/rt/5.0.0/web_deployment.html#nginx although I'm not sure if that sample config with fcgi would support the setup you had in mind. For RT version, I recommend targeting RT 5. Getting 4.0 era RT running on a new server is difficult (not impossible) because dependent modules have changed in the many years since it came out. I can help with the upgrade steps for the DB to get to 5.0. |
@cbrandtbuffalo Thank you for the offer! I have passed it along to davel, who is actually doing the code uplift and standup. I'm just doing the plumbing. :) |
Hi all, I have been working on getting the existing code working in a container. We're currently on 4.0.18 with various security patches. I'm hopeful it can work on a currently supported OS. @cbrandtbuffalo Thank you for the pointers! Are you able to offer any advice on plugin code compatibility when upgrading to 5.x? Should we consider moving to current 4.x before upgrading to 5.x? |
The ideal way for @bdha to support running RT is inside a Docker (or compatible) container. Ideally I could point an nginx or traefik server at an HTTP-speaking process in the container and go from there.
The text was updated successfully, but these errors were encountered: