Python feedback-tool包_程序模块 - PyPI

管理组织内部同行反馈的平台。

feedback-tool的Python项目详细描述

`feedback_tool`-简单的点对点反馈平台

feedback_tool是一个在组织。在

Docker快速入门

在
安装source-to-image
在
在
在本地Docker上运行应用程序
在

cd frontend
s2i build . centos/nodejs-8-centos7 feedback-tool-dev-frontend
cd ..
s2i build . centos/python-36-centos7 feedback-tool-app 
cd docker/dev
docker-compose up -d

设置一个虚拟模板，3个问题和周期数据来执行反馈循环。在

^{pr2}$

完全启动后，打开http://localhost:4200。请参阅docker/shared/ldif/01-data.ldif 用于虚拟用户的凭据。使用以下命令更改阶段。在

python tests/scripts/configure_db.py --config host_example.ini --subperiod enrollment adjust
python tests/scripts/configure_db.py --config host_example.ini --subperiod entry adjust
python tests/scripts/configure_db.py --config host_example.ini --subperiod approval adjust
python tests/scripts/configure_db.py --config host_example.ini --subperiod review adjust

配置值

`feedback_tool.db_url`

跟随http://docs.sqlalchemy.org/en/latest/core/engines.html#database-urls

`feedback_tool.business_unit`

显示在前端的标志旁边。对于多租户设置很有用在大公司内部。在

`feedback_tool.displayed_hostname`

如果设置，这将覆盖使用/etc/hostname作为主机名在电子邮件中显示到设置字符串。在

`feedback_tool.enable_send_email`

如果设置为true，则会导致发送电子邮件。发生这种情况：

当人才经理使用管理面板手动发送
如果 feedback_tool.run_email_interval_job配置值设置为true

`feedback_tool.production_hostname`和{}

如果这些值与应用程序在主机上看到的值匹配，则这将使：

加载给定业务部门的所有用户电子邮件，除非 feedback_tool.load_user_email_list已设置，则仅在列表中加载用户电子邮件的子集。在

^{}

The datetimes set in the Period table are technically not UTC. Those times are coupled with this configured value, the location. The phase shift will occur when a particular datetime is passed at this configured location.

Here are the available choices:

London
New York
Oxford
Shanghai
Hong Kong
GBR
Boston
Pfäffikon

^{}

Set this to an array of strings containing the LDAP usernames of who you would like to be able to login with the talent manager role. e.g. ["lcarty", "chasmith"]

^{}

This is normally set to ^{} as we now rely on talent managers uploading the user hierarchy configuration CSV into the application.

^{}

In non-prod environments, we don't save emails within the User database. If this is set, we will save the emails of the following list of users identified by their LDAP username, allowing them to be emailed (if emailing is turned on). e.g. ["chasmith"]

^{}

A useful development flag for impersonation. This should be set to ^{} in production.

^{}

If ^{}, run a job in the background that checks the email flags for the current period and if not set, send out the relevant emails and set.

^{}

Normally the company name, that will be displayed in the frontend.

^{}

Email that will be displayed to users when they are denied access to the tool or there is an unexpected error.

^{}

Email that will be displayed to users that they receive from the automated notification system (notifications sent by email).

^{}

Help message for the login input to remind users what username to use.

^{}

Help message for the login input to remind users what password to use.

^{}

Help message for talent manager on how to populate the CSV that is to be uploaded.

^{}

Help message for talent manager on how to generate the population CSV.

^{}

URI to LDAP instnace

^{}

LDAP field name for what to bind to the ^{} User model variable.

^{}

Template used to generate the bind DN for a user. Refer to the example config.

^{}