Feature #12340

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

Added by emmapeel 2017-03-14 08:35:31 . Updated 2019-06-27 17:16:44 .

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

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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

Subtasks

Related issues

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

History

#1 Updated by emmapeel 2017-03-14 10:30:47

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

#2 Updated by Anonymous 2017-12-19 16:43:46

  • Assignee deleted (emmapeel)

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 Anonymous 2018-01-17 13:37:02

#4 Updated by Anonymous 2018-03-02 15:22:46

  • Assignee set 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 Anonymous 2018-03-02 15:27:00

  • Assignee changed from bertagaz to groente

Sorry, I think this is for groente.

#6 Updated by Anonymous 2018-03-30 12:09:06

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 2018-04-13 10:36:32

  • Assignee deleted (groente)
  • 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 Anonymous 2018-04-24 14:42:43

  • Assignee set 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 Anonymous 2018-05-29 13:04:10

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

Please disregard this ticket in favor of Feature #15077.

#10 Updated by intrigeri 2019-06-27 17:16:44

  • Assignee deleted (groente)