[SAC] [OSGeo] #2740: Pretalx updates

#2740: Pretalx updates
---------------------------+-----------------------
Reporter: lucadelu | Owner: sac@…
     Type: task | Status: new
Priority: major | Milestone: Unplanned
Component: Systems Admin | Keywords: pretalx
---------------------------+-----------------------
Dear SAC,

could I ask to update pretalx container? The review pages is wrong
formatted and we would like to test if newer version resolve this problem.

Inside the deployment there all the submissions of FOSS4G 2022 so please
take care :slight_smile:

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2740&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2740: Pretalx updates
---------------------------+----------------------------------------
Reporter: lucadelu | Owner: sac@…
     Type: task | Status: new
Priority: major | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution:
Keywords: pretalx |
---------------------------+----------------------------------------
Changes (by robe):

* milestone: Unplanned => Sysadmin Contract 2022-II

Comment:

Okay I'll test on osgeo4 first.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2740#comment:1&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2740: Pretalx updates
---------------------------+----------------------------------------
Reporter: lucadelu | Owner: sac@…
     Type: task | Status: new
Priority: major | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution:
Keywords: pretalx |
---------------------------+----------------------------------------

Comment (by robe):

I started up https://talks.staging.osgeo.org

and upgraded the pretalx (main to latest pretalx docker image) and applied
latest main branch of public-voting and pages. I didn't restore data from
production since I didn't want any unintentional emails going out.
Hopefully this is good enough for you to test. If it looks good to you I
can install the same image on production.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2740#comment:2&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2740: Pretalx updates
---------------------------+----------------------------------------
Reporter: lucadelu | Owner: sac@…
     Type: task | Status: new
Priority: major | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution:
Keywords: pretalx |
---------------------------+----------------------------------------

Comment (by lucadelu):

It seems good to me, you can install the same image. Just to understand
better, are the data in a different container/image/database?

Thanks a lot

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2740#comment:3&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2740: Pretalx updates
---------------------------+----------------------------------------
Reporter: lucadelu | Owner: sac@…
     Type: task | Status: closed
Priority: major | Milestone: Sysadmin Contract 2022-II
Component: Systems Admin | Resolution: fixed
Keywords: pretalx |
---------------------------+----------------------------------------
Changes (by robe):

* status: new => closed
* resolution: => fixed

Comment:

Done.

The docker setup is composed of 3 containers:

1) pretalx (only one I updated)
2) mysql
3) redis

The data is stored in docker volumes and setup config in a folder so is
not gone when we swap out the images

The staging has different data from production (osgeo3-pretalx) and
staging is on a completely different server (its on osgeo4-pretalx-
staging). I use staging to build the docker images and then push it to
repo.osgeo.org (our local docker registry).

Then on production I pull down the latest built image from our local
docker registry and then run.

Steps are

{{{
#this is needed because takes a bit for things to start up
export COMPOSE_HTTP_TIMEOUT=100
docker pull docker.osgeo.org/sac/pretalx-osgeo:latest
docker-compose down
docker-compose up -d
docker-compose logs -f # to monitor things are running okay
}}}

hope that clarifies things

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2740#comment:4&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.