Project

General

Profile

Feature #12340

Feature #10034: Translation web platform

Feature #15079: Integrate the platform with our Git and ikiwiki infrastructure

Feature #15077: Have a staging website to build planned languages, with a resilient build

[translate.vm] give weblate permission to write to /var/lib/weblate/staging

Added by emmapeel over 2 years ago. Updated 5 months ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/14/2017
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

Weblate user (or maybe another user?) should be able to run ./build-website with destdir == /var/lib/weblate/staging


Related issues

Blocked by Tails - Feature #12342: [translate.vm]Decide if we merge 'weblate git' with 'staging git' Resolved 03/14/2017

History

#1 Updated by emmapeel over 2 years ago

  • Blocked by Feature #12342: [translate.vm]Decide if we merge 'weblate git' with 'staging git' added

#2 Updated by u almost 2 years ago

  • Assignee changed from emmapeel to u

Emmapeel: I think I will take care of this. We need to set up a meeting so that I can find out what's left to be done here and what this ticket is about.

#3 Updated by u almost 2 years ago

  • Parent task changed from #12311 to #15077

#4 Updated by u over 1 year ago

  • Assignee changed from u to bertagaz
  • QA Check deleted (Dev Needed)

This ticket would only be necessary if we have the staging website on the same VM but we havent' decided this yet.

#5 Updated by u over 1 year ago

  • Assignee changed from bertagaz to groente

Sorry, I think this is for groente.

#6 Updated by u over 1 year ago

I found this in /etc/apache2/sites-enabled/000-default.conf

    Alias /staging  /var/www/weblate/staging/
    #in this directory we will generate a staging version of the wiki
    <Directory /var/www/weblate/staging/>

Not sure how Apache starts without finding this repository, but it currently does not exist and I'm not sure if we want it to exist there or if it would be cleaner to put it under /var/www/staging.translate.b.o/ <- i like naming folders to indicate what they actually host personally.

#7 Updated by groente over 1 year ago

  • Assignee changed from groente to u
  • QA Check set to Info Needed

where does this apache config come from? i can't find any trace of it in puppet, was it created manually?

and to get back to the permission issue, is there any reason for the staging website to be owned by root (current situation) rather than weblate? a simple chown to weblate could fix the issue, but i'm not sure to what degree apache will need write permission on the staging site aswell?

#8 Updated by u over 1 year ago

  • Assignee changed from u to groente
  • QA Check changed from Info Needed to Dev Needed

groente wrote:

where does this apache config come from? i can't find any trace of it in puppet, was it created manually?

If there is no trace in puppet then probably yes. We should delete it from the production machine until we have puppet code for it and until we have tested it somewhere else.

and to get back to the permission issue, is there any reason for the staging website to be owned by root (current situation) rather than weblate? a simple chown to weblate could fix the issue, but i'm not sure to what degree apache will need write permission on the staging site aswell?

I think it should be owned by weblate, not root. Can you make that happen?

#9 Updated by u over 1 year ago

  • Status changed from Confirmed to Duplicate
  • QA Check deleted (Dev Needed)

Please disregard this ticket in favor of #15077.

#10 Updated by intrigeri 5 months ago

  • Assignee deleted (groente)

Also available in: Atom PDF