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