1361022 - Local localizer setup for Pontoon

Status: RESOLVED WORKSFORME

(Webtools Graveyard :: Pontoon, enhancement, P4)

Description

[Axel Hecht [:Pike]]

I've heard some interest in being able to set up pontoon locally, basically as an offline translation tool.

Maybe some docker-compose setup?

Things to make easy:

- Account handling
- vcs sync

CCing a few folks that I recall had interest in the workshop, did I miss features or folks?

Comment 1

[Francesco Lodolo [:flod]]

More specifically: Account handling without FxA (requires API key). I think you can add users manually from /a, but not sure that's documented anywhere, nor useful for this use case.

Background for this request: Pontoon is really slow from Asia (e.g. Taipei office).

Comment 2

[Peter Pin-Guang Chen [:petercpg] (MozTW.org)]

CC Matjaz and Tim as I talked similar idea to them in Hawaii. 

Agree that db sync would be painful in my original idea (setting up a Pontoon installation somewhere in Asia with same db connection). Making it work offline and sync later would be easier.

(In reply to Axel Hecht [out-of-office -May 2nd][:Pike] from comment #0)
> I've heard some interest in being able to set up pontoon locally, basically
> as an offline translation tool.
> 
> Maybe some docker-compose setup?
> 
> Things to make easy:
> 
> - Account handling

Aren't we using Firefox Account already?

> - vcs sync
> 
> CCing a few folks that I recall had interest in the workshop, did I miss
> features or folks?

Probably one more feature, to show attribution for approved (committed) translation imported from VCS instead of "Imported x years ago"? Or is that included in "vcs sync" part?

Comment 3

[Axel Hecht [:Pike]]

I filed this bug to specifically track the things we need to run pontoon on a laptop on the plane.

There's obviously the other side of things where other systems reading back from VCS aren't great, like bug 1293039. I think that these bugs shouldn't block us.

Comment 4

[Matjaz Horvat [:mathjazz]]

I'd like to learn more about the motivation for this. If performance is the primary reason, I want to make sure fixing bug 1344658 (and other performance bugs like bug 1344658) will not have a greater impact than running a local instance. The main Pontoon performance issues are likely to be independent of the region.

(In reply to Axel Hecht [out-of-office -May 2nd][:Pike] from comment #0)
> - Account handling

There's `DJANGO_LOGIN` setting if you want to use the default Django login instead of Firefox Accounts:
http://mozilla-pontoon.readthedocs.io/en/latest/dev/install.html#extra-settings

> - vcs sync

By default, local setup will not sync. You'd either need to run the management command every time you want to sync or enable the `Sync` button in Admin by setting `MANUAL_SYNC` to True. What else related to sync needs to be taken care of?

Comment 5

[Staś Małolepszy :stas]

I'm not sure how relevant it is today but last year I created https://gist.github.com/stasm/97a5b56587fcd5850cd14fe6f91fe7c8 with instructions about how to set up a local instance of Pontoon using Docker.

Comment 6

[Matjaz Horvat [:mathjazz]]

Is there anything in here besides what's now covered by bug 1376813?

Comment 7

[Axel Hecht [:Pike]]

I would argue that we need to get a sequence of dogfood going. And then document the pitfalls that we can shell out to different bugs.

Comment 8

[[DEACTIVATED] Adrian Gaudebert]

That doesn't sound like a very actionable bug. Dogfooding won't happen if we don't advertise the existence of the docker install, though as far as I know we do have a bunch of users - flod, myself, and at least another contributor who's name I forgot. 

Axel, are there any actions you were thinking about that we could do today? If not, I think I'd advise we close this bug and wait for users to run into issues and file new bugs.

Comment 9

[Matjaz Horvat [:mathjazz]]

There's lots of things covered by this bug, most of which seem fixed.

Let's file more concrete bugs for the remainder of work if needed.