[Sugar-devel] Pootle SOS
Martin Abente
martin.abente.lahaye at gmail.com
Thu Jul 31 13:48:55 EDT 2014
Hey guys,
A few updates:
- I just finished upgrading the exiting instance to Pootle 2.5.1.1 [1].
I don't know exactly what can I test to make sure the upgrade is working
properly, @cjl suggestions?
- Next step would be a fix version control integration.
A few concerns:
- This update process feels like walking in the dark, the documentation
does not help much to understand what is expected to work or what are the
uses cases for our instance.
- I honestly worry that maintaining the current instance (upgraded or
not) will not be possible in the long term.
How about a meeting this Wednesday, August 6? To discuss about these
concerns and possible alternatives.
*Refs:*
1. http://newpootle.sugarlabs.org/about/
On Thu, Jul 31, 2014 at 2:21 AM, Matthew Ciao <matthew at laptop.org.au> wrote:
> Let me know if you need any help up there Martin... Django can be a
> serious pain in the deck. :)
>
> Cheers
>
>
>
> On 31 July 2014 00:25, Martin Abente <martin.abente.lahaye at gmail.com>
> wrote:
>
>> Hey Matthew,
>>
>> Thanks! Right now I am trying to figure out how to upgrade pootle
>> packages, but after I am done we look at that :)
>>
>>
>> On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao <matthew at laptop.org.au>
>> wrote:
>>
>>> Hi Martin,
>>>
>>> maybe if you have time you / we can also work out a minimal secure
>>> setup?
>>>
>>> Looks like newpootle needs a bit of firewalling to start with:
>>>
>>> sudo /sbin/iptables -L -nv
>>> Chain INPUT (policy ACCEPT 324 packets, 29890 bytes)
>>> pkts bytes target prot opt in out source
>>> destination
>>>
>>> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>>> pkts bytes target prot opt in out source
>>> destination
>>>
>>> Chain OUTPUT (policy ACCEPT 186 packets, 20370 bytes)
>>> pkts bytes target prot opt in out source
>>> destination
>>>
>>> Cheers
>>>
>>>
>>> On 30 July 2014 17:46, Matthew Ciao <matthew at laptop.org.au> wrote:
>>>
>>>> Thanks Bernie!
>>>>
>>>> Martin I enclose an apache vhost .conf file that should work out of the
>>>> box based on my reading/editing of the one in production at the moment.
>>>>
>>>> There are a few edits so if you intend to use it please remove my
>>>> comments! :D
>>>>
>>>> Cheers
>>>>
>>>>
>>>> On 30 July 2014 12:28, Bernie Innocenti <bernie at codewiz.org> wrote:
>>>>
>>>>> Try logging in as bashintosh at newpootle.sugarlabs.org
>>>>>
>>>>> You have root on newpootle, but please coordinate with Martin to avoid
>>>>> stepping on each other's toes :-)
>>>>>
>>>>> On 07/29/2014 06:42 PM, Matthew Ciao wrote:
>>>>> > Hi Martin,
>>>>> >
>>>>> > do you have any .htaccess files in your sites directories?
>>>>> >
>>>>> > If yes you need to review the AllowOverride directive in your config
>>>>> > files and depending on what is in .htaccess you may need to enable
>>>>> > modules such as mod_rewrite.
>>>>> >
>>>>> > Anyway the first deny directive you have there works for the main
>>>>> Apache
>>>>> > document-root (/) which I assume is /srv/www/ itself: check your
>>>>> > httpd.conf (or main config file under /etc/apache2/) and look for the
>>>>> > default document-root.
>>>>> >
>>>>> > Creating an exception as you did to allow access for /srv/www/ works
>>>>> but
>>>>> > that way you slow down Apache a bit because first it evaluates a deny
>>>>> > then an allow directive for the same document-root.
>>>>> >
>>>>> > If you post all the config files we can understand even better.. :)
>>>>> >
>>>>> > Cheers
>>>>> >
>>>>> > On Wednesday, 30 July 2014, Martin Abente
>>>>> > <martin.abente.lahaye at gmail.com
>>>>> > <javascript:_e(%7B%7D,'cvml','martin.abente.lahaye at gmail.com');>>
>>>>> wrote:
>>>>> >
>>>>> > Hello all,
>>>>> >
>>>>> > The instance is back, I had to made a few changes:
>>>>> >
>>>>> > 1. added ".conf" extension to the site configuration file
>>>>> > 2. temporarily removed caching directives, I still need to
>>>>> figure
>>>>> > what can be use to replace them.
>>>>> > 3. changed some permissions [1].
>>>>> >
>>>>> >
>>>>> > @matthew can you re-check the configuration file? I am not
>>>>> expert in
>>>>> > apache so my fixes could be more like hacks.
>>>>> >
>>>>> > Next step is trying to upgrade pootle version...
>>>>> >
>>>>> > Refs:
>>>>> > 1.
>>>>> >
>>>>> http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/
>>>>> >
>>>>> >
>>>>> > On Mon, Jul 28, 2014 at 9:41 PM, Matthew Ciao
>>>>> > <matthew at laptop.org.au> wrote:
>>>>> >
>>>>> > Done!
>>>>> >
>>>>> > Sent it from my private email bashintosh at gmail dot com
>>>>> >
>>>>> > On 29 July 2014 10:43, Bernie Innocenti <bernie at codewiz.org>
>>>>> wrote:
>>>>> >
>>>>> > By the way, you don't even have a shell account yet:
>>>>> >
>>>>> > http://wiki.sugarlabs.org/go/Service/shell
>>>>> >
>>>>> > Please apply now, you can use me as your sponsor.
>>>>> >
>>>>> > On 07/28/2014 07:52 PM, Matthew Ciao wrote:
>>>>> > > As a quick suggestion, if you haven't done it already I
>>>>> > recommend to
>>>>> > > start debugging by looking at the Apache logs
>>>>> > (/var/log/apache2 on most
>>>>> > > Debian-based systems).
>>>>> > >
>>>>> > > A general health-check on Apache itself could also
>>>>> include:
>>>>> > >
>>>>> > > * verify the server is running (process)
>>>>> > > * verify the server is listening on the desired ports
>>>>> > (netstat, lsof)
>>>>> > > * check firewall rules (iptables being a good place
>>>>> to
>>>>> > start)
>>>>> > > * inspect vhosts configurations
>>>>> > >
>>>>> > > Lemme know if you need any help Martin,
>>>>> > >
>>>>> > > /Matthew/
>>>>> > >
>>>>> > >
>>>>> > > On 29 July 2014 01:27, Martin Abente
>>>>> > <martin.abente.lahaye at gmail.com
>>>>> > > <mailto:martin.abente.lahaye at gmail.com>> wrote:
>>>>> > >
>>>>> > > Ok!
>>>>> > >
>>>>> > >
>>>>> > > On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti
>>>>> > > <bernie at codewiz.org <mailto:bernie at codewiz.org>>
>>>>> wrote:
>>>>> > >
>>>>> > > Yes, I did it yesterday. The machine boots, but
>>>>> > the apache
>>>>> > > virtual host
>>>>> > > doesn't seem to work any more.
>>>>> > >
>>>>> > > I'll leave the rest to you!
>>>>> > >
>>>>> > >
>>>>> > > On 07/28/2014 10:53 AM, Martin Abente wrote:
>>>>> > > > Hey Bernie!
>>>>> > > >
>>>>> > > > Did you get the time to update the machine?
>>>>> > > >
>>>>> > > >
>>>>> > > > On Thu, Jul 24, 2014 at 7:56 PM, Matthew Ciao
>>>>> > > <matthew at laptop.org.au <mailto:
>>>>> matthew at laptop.org.au>
>>>>> > > > <mailto:matthew at laptop.org.au
>>>>> > <mailto:matthew at laptop.org.au>>>
>>>>> > > wrote:
>>>>> > > >
>>>>> > > > Guys please let me know if there's
>>>>> anything
>>>>> > I can do to help!
>>>>> > > >
>>>>> > > >
>>>>> > > > On 25 July 2014 04:01, Martin Abente
>>>>> > > <martin.abente.lahaye at gmail.com
>>>>> > > <mailto:martin.abente.lahaye at gmail.com>
>>>>> > > > <mailto:martin.abente.lahaye at gmail.com
>>>>> > > <mailto:martin.abente.lahaye at gmail.com>>>
>>>>> wrote:
>>>>> > > >
>>>>> > > > Hey Bernie!
>>>>> > > >
>>>>> > > > I (literally) just finished my first
>>>>> > round of tests
>>>>> > > setting up a
>>>>> > > > pootle 2.5.1.1 instance from scratch.
>>>>> > The results are
>>>>> > > promising:
>>>>> > > >
>>>>> > > > 1. Setting up a pootle instance from
>>>>> > scratch was very
>>>>> > > > straightforward.
>>>>> > > > 2. Creating a new project and
>>>>> > integrating it with git
>>>>> > > > versioning was also surprisingly
>>>>> > straightforward.
>>>>> > > In fact,
>>>>> > > > no custom bits were require to
>>>>> make
>>>>> > pootle import
>>>>> > > Sugar
>>>>> > > > project and start making commits
>>>>> to
>>>>> > the remote
>>>>> > > repository.
>>>>> > > >
>>>>> > > > Other premature comments:
>>>>> > > >
>>>>> > > > * pootle imported _almost_ all the
>>>>> > languages, but I
>>>>> > > had to
>>>>> > > > manually add languages like
>>>>> > "guarani". I still
>>>>> > > don't know
>>>>> > > > why, ideas?
>>>>> > > > * I still need to check the SL
>>>>> wiki to
>>>>> > have some
>>>>> > > ideas of how
>>>>> > > > it would be better to organize
>>>>> the
>>>>> > projects. IIRC, our
>>>>> > > > previous pootle instance followed
>>>>> > the same sugar
>>>>> > > modules
>>>>> > > > like sucrose, fructose, etc.
>>>>> > Suggestions?
>>>>> > > >
>>>>> > > >
>>>>> > > > I don't think I will have the time to
>>>>> > work on this
>>>>> > > during the
>>>>> > > > weeking (because of the wedding),
>>>>> but if
>>>>> > you could
>>>>> > > make sure the
>>>>> > > > server is ready, I can continue over
>>>>> the
>>>>> > week.
>>>>> > > >
>>>>> > > >
>>>>> > > > Bernie if you don't have time to work on
>>>>> > what Martin needs
>>>>> > > I can
>>>>> > > > step in, no problems at all.
>>>>> > > >
>>>>> > > > Cheers!
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > > > On Thu, Jul 24, 2014 at 1:03 PM,
>>>>> Bernie
>>>>> > Innocenti
>>>>> > > > <bernie at codewiz.org
>>>>> > <mailto:bernie at codewiz.org>
>>>>> > > <mailto:bernie at codewiz.org
>>>>> > <mailto:bernie at codewiz.org>>> wrote:
>>>>> > > >
>>>>> > > > Martin is taking Pootle, but if
>>>>> you
>>>>> > have time to
>>>>> > > help with
>>>>> > > > it, I think
>>>>> > > > it would be appreciated.
>>>>> > > >
>>>>> > > > I think I'll start the work on
>>>>> > Sunday. Martin,
>>>>> > > would you
>>>>> > > > have time?
>>>>> > > >
>>>>> > > >
>>>>> > > > On 07/21/2014 07:08 AM, Matthew
>>>>> Ciao
>>>>> > wrote:
>>>>> > > > > Hi folks,
>>>>> > > > >
>>>>> > > > > it looks like you're already
>>>>> in a
>>>>> > good position
>>>>> > > in terms
>>>>> > > > of help from
>>>>> > > > > rgs and/or icarito so I don't
>>>>> > think I would be
>>>>> > > very useful
>>>>> > > > at the meeting.
>>>>> > > > >
>>>>> > > > > This said, if all goes bad
>>>>> please
>>>>> > involve me in
>>>>> > > the Pootle
>>>>> > > > mission as I
>>>>> > > > > am more than keen to lend a
>>>>> hand! :)
>>>>> > > > >
>>>>> > > > > Best,
>>>>> > > > >
>>>>> > > > > Matthew
>>>>> > > > >
>>>>> > > > > On Jul 21, 2014 4:15 AM,
>>>>> "Bernie
>>>>> > Innocenti"
>>>>> > > > <bernie at codewiz.org
>>>>> > <mailto:bernie at codewiz.org>
>>>>> > > <mailto:bernie at codewiz.org
>>>>> > <mailto:bernie at codewiz.org>>
>>>>> > > > > <mailto:bernie at codewiz.org
>>>>> > > <mailto:bernie at codewiz.org> <mailto:
>>>>> bernie at codewiz.org
>>>>> > > <mailto:bernie at codewiz.org>>>>
>>>>> > > > wrote:
>>>>> > > > >
>>>>> > > > > +rgs, +icarito (both of
>>>>> which
>>>>> > expressed
>>>>> > > interest in
>>>>> > > > supporting Pootle)
>>>>> > > > >
>>>>> > > > >
>>>>> > > > > On 07/20/2014 01:36 PM,
>>>>> Martin
>>>>> > Abente wrote:
>>>>> > > > > > Hello everyone,
>>>>> > > > > >
>>>>> > > > > > What about investing some
>>>>> > minutes this
>>>>> > > week to talk
>>>>> > > > about Pootle's
>>>>> > > > > > status, what is missing
>>>>> and
>>>>> > how can we get
>>>>> > > it back
>>>>> > > > to life?
>>>>> > > > > >
>>>>> > > > > > I suggest this Wednesday
>>>>> 23
>>>>> > July, 13:00 UTC.
>>>>> > > > >
>>>>> > > > > It's a bit early for me,
>>>>> and
>>>>> > definitely too
>>>>> > > early for rgs.
>>>>> > > > > Can we do 15:00 UTC?
>>>>> > > > >
>>>>> > > > >
>>>>> > > > > In case I miss the meeting,
>>>>> > here's a full
>>>>> > > dump of my mind:
>>>>> > > > >
>>>>> > > > > - you, rgs and icarito
>>>>> > already have root to
>>>>> > > > newpootle.sugarlabs.org
>>>>> > <http://newpootle.sugarlabs.org>
>>>>> > > <http://newpootle.sugarlabs.org>
>>>>> > <http://newpootle.sugarlabs.org>
>>>>> > > > > <
>>>>> http://newpootle.sugarlabs.org>
>>>>> > > > >
>>>>> > > > > - full backups of the old
>>>>> > pootle machine are on
>>>>> > > > freedom, and all of you
>>>>> > > > > have root access there too
>>>>> > > > >
>>>>> > > > > - Sysadmin documentation
>>>>> is
>>>>> > in the usual
>>>>> > > place (the
>>>>> > > > wiki). There are
>>>>> > > > > several pages written by
>>>>> the
>>>>> > previous Pootle
>>>>> > > maintainers:
>>>>> > > > >
>>>>> > > > >
>>>>> > http://wiki.sugarlabs.org/go/Service/translate
>>>>> > > > >
>>>>> > http://wiki.sugarlabs.org/go/Service/Pootle
>>>>> > > > >
>>>>> > http://wiki.sugarlabs.org/go/Service/Pootle2.5
>>>>> > > > >
>>>>> > http://wiki.sugarlabs.org/go/Machine/pootle
>>>>> > > > >
>>>>> > > > > The documentation needs
>>>>> to be
>>>>> > consolidated
>>>>> > > into a
>>>>> > > > single page and
>>>>> > > > > updated. *PLEASE*, don't
>>>>> > neglect this step;
>>>>> > > it will
>>>>> > > > save a lot of time
>>>>> > > > > to future maintainers.
>>>>> > > > >
>>>>> > > > > - The newpootle machine is
>>>>> > still running
>>>>> > > Ubuntu 12.04
>>>>> > > > LTS. I strongly
>>>>> > > > > recommend upgrading it to
>>>>> > 14.04 (trusty) before
>>>>> > > > proceeding. It won't
>>>>> > > > > take more than 1h of work
>>>>> and
>>>>> > I can do this.
>>>>> > > > >
>>>>> > > > > - There's an outdated
>>>>> > instance of Pootle
>>>>> > > already
>>>>> > > > running on newpootle.
>>>>> > > > > It was setup by a previous
>>>>> > volunteer, but never
>>>>> > > > transitioned into
>>>>> > > > > production due to
>>>>> difficulties
>>>>> > with the git
>>>>> > > > integration (iirc, cjl might
>>>>> > > > > have more on this).
>>>>> > > > >
>>>>> > > > > - I strongly recommend
>>>>> > upgrading to the latest
>>>>> > > > release of Pootle before
>>>>> > > > > doing anything else.
>>>>> > > > >
>>>>> > > > > - Then, the database and
>>>>> data
>>>>> > from the
>>>>> > > backups needs
>>>>> > > > to be restored and
>>>>> > > > > probably converted to the
>>>>> > Pootle 2.5 format
>>>>> > > (good luck
>>>>> > > > with Django db
>>>>> > > > > migration!)
>>>>> > > > >
>>>>> > > > > - Finally, the part where
>>>>> all
>>>>> > past
>>>>> > > maintainers seem
>>>>> > > > to get stuck: make
>>>>> > > > > the Pootle <-> git
>>>>> integration
>>>>> > work. I don't
>>>>> > > know what
>>>>> > > > the actual
>>>>> > > > > problem is; pushing to git
>>>>> > should be a basic
>>>>> > > feature
>>>>> > > > of a translation
>>>>> > > > > system and I'm surprised
>>>>> this
>>>>> > can't be made
>>>>> > > to work
>>>>> > > > out of the box.
>>>>> > > > >
>>>>> > > > > - When everything works
>>>>> (and
>>>>> > please test it
>>>>> > > well,
>>>>> > > > Pootle likes to crash
>>>>> > > > > and burn under load), we
>>>>> can
>>>>> > change the DNS
>>>>> > > to point
>>>>> > > > the CNAME
>>>>> > > > > translate.sugarlabs.org
>>>>> > <http://translate.sugarlabs.org>
>>>>> > > <http://translate.sugarlabs.org>
>>>>> > > > <http://translate.sugarlabs.org>
>>>>> > > > <http://translate.sugarlabs.org>
>>>>> to
>>>>> > > > > newpootle. Follow the
>>>>> > Service/nameserver
>>>>> > > > > documentation page to do
>>>>> this,
>>>>> > or I can do
>>>>> > > it in 2
>>>>> > > > minutes.
>>>>> > > > >
>>>>> > > > > --
>>>>> > > > > _ // Bernie Innocenti
>>>>> > > > > \X/ http://codewiz.org
>>>>> > > > >
>>>>> > > >
>>>>> > > >
>>>>> > > > --
>>>>> > > > _ // Bernie Innocenti
>>>>> > > > \X/ http://codewiz.org
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > >
>>>>> > >
>>>>> > > --
>>>>> > > _ // Bernie Innocenti
>>>>> > > \X/ http://codewiz.org
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > _ // Bernie Innocenti
>>>>> > \X/ http://codewiz.org
>>>>> >
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>> --
>>>>> _ // Bernie Innocenti
>>>>> \X/ http://codewiz.org
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140731/3b49b819/attachment-0001.html>
More information about the Sugar-devel
mailing list