Opened 5 years ago

Closed 5 years ago

#11122 closed task (fixed)

Document webchat setup

Reported by: lunar Owned by: Phoul
Priority: Medium Milestone:
Component: User Experience/Tor Support Version:
Severity: Keywords: SponsorO
Cc: Sherief Actual Points:
Parent ID: #10755 Points:
Reviewer: Sponsor:

Description

The whole setup should be documented, probably on the wiki, probably linked/close to org/operations/Infrastructure.

Child Tickets

Change History (9)

comment:1 Changed 5 years ago by lunar

Owner: set to Phoul
Status: newassigned

As discussed during the meeting on March 7th.

comment:2 Changed 5 years ago by lunar

Any progress?

comment:3 Changed 5 years ago by Sherief

Cc: Sherief added

comment:4 Changed 5 years ago by Sherief

My part will be: Writing the list of requirements and how to deploy pups. It should be ready by Thursday (2014-05-01).

comment:5 Changed 5 years ago by phoul

I have put this document at https://trac.torproject.org/projects/tor/wiki/infrastructure/support.torproject.org for now. Sherief, feel free to add your pups deployment information to this page.

comment:6 in reply to:  5 Changed 5 years ago by Sherief

Replying to phoul:

I have put this document at https://trac.torproject.org/projects/tor/wiki/infrastructure/support.torproject.org for now. Sherief, feel free to add your pups deployment information to this page.

Done. Please review.

comment:7 Changed 5 years ago by lunar

The example configuration for Apache and Prosody contains too much of the Debian package defaults. Highlighting only the changes needed to run the application would be better.

With the apache2 Debian package, VirtualHosts usually each gets their own file in the /etc/apache2/sites-available directory. To be enabled using the a2ensite/a2dissite commands.

The prosody Debian package also features a conf-available directory IIRC.

comment:8 Changed 5 years ago by phoul

This is part of why each of the configurations has a note under them stating that they will be replaced with the running config once it is deployed. If you want only the changes to be shown for the Apache2 and Prosody configs, how would you like this done? A diff to the Debian default? Are there any examples of this for our other infrastructure?

I have replaced the Apache config on that page with the sites-available configuration that will likely be running on Moschatum.

Last edited 5 years ago by phoul (previous) (diff)

comment:9 Changed 5 years ago by phoul

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.