#5530 Upgrade taiga.fedorainfracloud.org to taiga 3
Closed 7 years ago Opened 7 years ago by ralph.

This ticket supersedes #5214.

Taiga 3 came out and apparently it is "very nice" - much improved over the 2.x line.

We have a taiga-stg instance we could try this out on, and if it goes well, update the prod taiga.fedorainfracloud.org instance.

Note, since taiga lives under the fedorainfracloud.org domain, it is technically unsupported. I set it up and maintain it on a best-effort basis.

People are requesting that we do the upgrade. We do indeed backup the database and have the ability to recover from an outage, but there are effectively 0 full-time humans dedicated to supporting the instance.

I can do this upgrade at some point, but I can't say exactly when yet. (when there is some free time ;p).

I'm filing this ticket as a tracker so people who ask for an upgrade can watch here.


Update to the Taiga 3 would be really appreciated. Ralph, do you have to update it or can we ask someone else for help if you are busy?

I don't have to be the one, but I'm the only one familiar with it (others would have to learn how it is setup first, and then do the upgrade).

If multiple parties are interested in an upgrade (which seems to be the case), then I can prioritize it.

Saw the demo, love the features.

+1

+1 for the upgrade, there are new features which I am interested in

taiga staging is upgraded to latest stable release now.

one "minor" change is that the landing page is not the fas-login page, but still can login with fas...this need further looking!

please give it a spin at: https://taigastg.fedorainfracloud.org
have fun and update this issue track with fidings

The ssl cert seems to be expired. ;( There should be a cron setup to renew...

Otherwise it looks pretty nice to me. :no_mouth:

Thanks, seems to be working.

I modified the taiga playbook/role... and ready to push the updates.
however, we need to add two things to private ansible
1-private/passwords.yml,taiga_admin_pw: hashed password to replace the default password
2-copy over the cert files/folders to {{private}}/files/letsencrypt/{{inventory_hostname}}/ for both stag and prod

with today's discussion, I've removed the tasks to backup the letsencrypt certs.
the rest of the changes have been reviewed by threebean

We looked at this in IRC, but now I can't find a link to the patch.

@doteast, can you link me to it?

link to the diff of my commits, and are ready to push.

http://paste.fedoraproject.org/488655/85325814/

Sorry @doteast, it seems the patch does not apply. Can you try rebasing against master and posting a new version?

$ curl https://paste.fedoraproject.org/488655/85325814/raw/ | git apply
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  5693  100  5693    0     0  42851      0 --:--:-- --:--:-- --:--:-- 43128
<stdin>:14: trailing whitespace.
#renew letsencrypt certificate. it checks if cert need renewal. if not nginx will not stop
<stdin>:15: trailing whitespace.
# check and renew if required, quietly. if so do it in standalone mode
<stdin>:29: trailing whitespace.
# change default admin password
<stdin>:30: trailing whitespace.
- name: change admin password
<stdin>:31: trailing whitespace.
  command : sudo -u taiga sed -i -e 's/\"pbkdf2_sha256.*\"/\"{{taiga_admin_pw}}\"/' /home/taiga/taiga-back/taiga/users/fixtures/initial_user.json
error: patch failed: roles/taiga/files/renew-cert.sh:1
error: roles/taiga/files/renew-cert.sh: patch does not apply
error: patch failed: roles/taiga/tasks/main.yml:117
error: roles/taiga/tasks/main.yml: patch does not apply
error: patch failed: roles/taiga/templates/conf.json:2
error: roles/taiga/templates/conf.json: patch does not apply
error: patch failed: roles/taiga/templates/taiga-ssl.nginx:38
error: roles/taiga/templates/taiga-ssl.nginx: patch does not apply

sorry, but that was because it was not in patch format to apply, but commit-diff for review, typically with line wrapping.

updates are now pushed.

thanx

OK, we're aiming to do the upgrade 2016-11-30 at 18:30 UTC.

See #5582.

Allright, #5582 is done now and we're upgraded to taiga3.

Let us know if you encounter any issues.

(You may need to ask your browser to do a hard-reload to get the new css assets).

Allright, #5582 is done now and we're upgraded to taiga3.

Let us know if you encounter any issues.

(You may need to ask your browser to do a hard-reload to get the new css assets).

@ralph changed the status to Closed

7 years ago

Login to comment on this ticket.

Metadata