[PATCH] Add defaults var for fas_client
by Nicolas Chauvet
v2: fix inverted fas_staging_url/fas_url
---
roles/fas_client/defaults/main.yml | 8 ++++++++
roles/fas_client/templates/fas.conf.j2 | 8 ++++----
2 files changed, 12 insertions(+), 4 deletions(-)
create mode 100644 roles/fas_client/defaults/main.yml
diff --git a/roles/fas_client/defaults/main.yml b/roles/fas_client/defaults/main.yml
new file mode 100644
index 0000000..f0983d2
--- /dev/null
+++ b/roles/fas_client/defaults/main.yml
@@ -0,0 +1,8 @@
+---
+# defaults file for fas_client
+#
+
+fas_url: https://admin.fedoraproject.org/accounts/
+fas_staging_url: https://admin.stg.fedoraproject.org/accounts/
+fas_home: /home/fedora
+fas_home_backup_dir: "{{ fas_home }}.bak"
diff --git a/roles/fas_client/templates/fas.conf.j2 b/roles/fas_client/templates/fas.conf.j2
index a27f0ef..2824339 100644
--- a/roles/fas_client/templates/fas.conf.j2
+++ b/roles/fas_client/templates/fas.conf.j2
@@ -1,9 +1,9 @@
[global]
; url - Location to fas server
{% if env == "staging" %}
-url = https://admin.stg.fedoraproject.org/accounts/
+url = {{ fas_staging_url }}
{% else %}
-url = https://admin.fedoraproject.org/accounts/
+url = {{ fas_url }}
{% endif %}
; temp - Location to generate files while user creation process is happening
@@ -59,11 +59,11 @@ aliases_template = /etc/aliases.template
shell = /bin/bash
; home - the location for fas user home dirs
-home = /home/fedora
+home = {{ fas_home }}
; home_backup_dir - Location home dirs should get moved to when a user is
; deleted this location should be tmpwatched
-home_backup_dir = /home/fedora.bak
+home_backup_dir = {{ fas_home_backup_dir }}
; ssh_restricted_app - This is the path to the restricted shell script. It
; will not work automatically for most people though through alterations it
--
1.7.2.1
8 years, 6 months
Badges for translations contribution
by Alex Eng
Hi
I'm Alex from Zanata team.
We've recently discussed on getting Zanata webhook to trigger event
for Fedora badges.
Just wondering who is the best person to talk to?
1) What sort of details does Zanata need to include in the event?
2) Any test instance which we can test the event on?
---------------------------------------------
Alex Eng
Globalisation Tools Engineering
DID: +61 3514 8262 <callto:+61+3514+8262>
Mobile: +614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd
Level 1, 193 North Quay
Brisbane 4000
Office: +61 7 3514 8100 <callto:+61+7+3514+8100>
Fax: +61 7 3514 8199 <callto:+61+7+3514+8199>
Website: www.redhat.com
8 years, 6 months
Migration to HyperKitty / Mailman 3
by Aurelien Bompard
Hi people!
Since it's Friday evening, I just unilateraly decided to migrate all
the lists to Mailman3 without telling you anything in advance... Nah
just kidding :-)
However, I think the best time to migrate the rest of the lists would
be the week before Thanksgiving. That would give me some time with you
all around to fix the most urgent problems, and time for me during a
week with less activity in the US to fix the lower priority ones.
Some lists are still using the two features that are not yet ported,
namely the filters and the topics. Those lists would stay on the
current server for now, but migrating the rest would still be an
improvement. This would mean migration would start on November 16th.
What do you think?
I'm also trying to write an announcement for the lists (like
devel-announce), but I'm looking for a native english speaker to help
me with that. It would be something like :
----------------
Dear list users,
The Fedora Engineering team has been working on a new system for our
mailing lists. Mailman 3 came out earlier this year and it has a new
shiny web UI: HyperKitty.
The Fedora project lists will be migrated starting November 16th. You
on't have to use the new UI to keep participating in the
mailing-lists, but the change to Mailman 3 may cause issues with the
way you filter your email. Here are a few things you should expect
after this change, especially if you're using procmail for filtering:
http://fedoraproject.org/wiki/Mailman3_Migration. But it should mostly
work as before.
A link to HyperKitty will be included in the email footers when your
list is migrated.
Some lists which use Mailman 2.1's advanced filtering capabilities (by
header or by topic) will remain on the current version until these
features are ported to Mailman 3.
If you have any questions, feel free to ask on the infrastructure
list: infrastructure(a)lists.fedoraproject.org.
------------------
Am I missing important information? Feel free to reword things if they
are not clear or if it's just bad style.
Thanks !
Aurélien
8 years, 6 months
Looks like EOL script was run with the wrong close reason
by Matthew Miller
Seems like everything got "CLOSED:WONTFIX" instead of "CLOSED:EOL". I
suppose it's not worth creating double churn to correct that, but it
makes me sad. What needs to change to make sure it happens the right
way next time?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
8 years, 6 months