txbr 1.0.0

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: ad8a2929f789e8df389eba18aab034fbd3c089306ef86b86e496859196088aea
4
+ data.tar.gz: ab4a6147c75a7432e2ef0b34c30efdd5949cd1a07b774eae1d84e953a0c7d111
5
+ SHA512:
6
+ metadata.gz: 93871ba2e176ff5c9fcf85a9a521fd209fbec9599f286fb52be30f447bc1016a31d2a93587a918ebd7a4a55d80935a4ae9b79256460bc1f0f26ec5bb187b310b
7
+ data.tar.gz: 38b3253c2bfaa7053c9605c7bc7e861d86b3d702ab63acd27ee78c6e0e264f7e6406473d52880c952c7a0d259ba990e28c6fc33cc74740657fad7f2f6c2009a1
data/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "{}"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright {yyyy} {name of copyright owner}
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
202
+
@@ -0,0 +1,137 @@
1
+ Txbr
2
+ ====
3
+
4
+ [![Build Status](https://travis-ci.org/lumoslabs/txbr.svg?branch=master)](https://travis-ci.org/lumoslabs/txbr)
5
+
6
+ Txbr, a mashup of "Transifex" and "Braze", is an automation tool that facilitates translating Braze content (emails, push notifications, etc) with Transifex, a popular translation management system.
7
+
8
+ How does it work?
9
+ ---
10
+
11
+ Txbr looks for specific Liquid tags in your email templates, push notifications, etc to know what translations your template contains and where to store them in Transifex. Txbr extracts source language strings (i.e. strings in English) from your templates and creates resources in Transifex. Once translations are ready, you can use Braze's Connected Content feature to make them available in your template.
12
+
13
+ Here's an example template for the impatient:
14
+
15
+ ```liquid
16
+ <html>
17
+ <head>
18
+ {% assign project_slug = "my_transifex_project" %}
19
+ {% assign resource_slug = "my_transifex_resource" %}
20
+ {% connected_content https://your_txbr_server.com/strings.json?project_slug={{project_slug}}&resource_slug={{resource_slug}}&locale={{${language} | default: 'en'}}&strings_format=YML :basic_auth txbr :save strings %}
21
+ </head>
22
+ <body>
23
+ {{strings.header.title | default: "Buy my stuff!"}}
24
+ </body>
25
+ </html>
26
+ ```
27
+
28
+ There are several important bits in the example above:
29
+
30
+ 1. Every template you would like Txbr to manage must contain these three required Liquid tags: `assign project_slug`, `assign resource_slug`, and `connected_content`. The first two correspond to the Transifex project and resource in which you would like to store the template's strings, and the third is the mechanism by which translations are fetched and inserted into the template when it is previewed or delivered.
31
+ 2. The project slug should correspond to a valid Transifex project. You'll need to create the project in Transifex, then copy the slug from the URL.
32
+ 3. The resource slug should be unique within the Transifex project and must only contain uppercase and lowercase letters, numbers, underscores (i.e. "_"), and dashes (i.e. "-"). It's a safe bet to simply use the template's API identifier found at the bottom of the template's configuration page. Txbr itself places no restrictons on and performs no validation against this field, so it can contain any custom slug you want.
33
+ 4. The `connected_content` tag fetches translated content from Transifex using the project and resource slugs you assigned earlier in the locale of the "current" user. When previewing your template, the locale can be set in the left-hand sidebar via a simulated current user.
34
+ 5. Notice the `{{strings.header.title | default: "Buy my stuff!}}` tag. This defines and fetches a string at the key `header.title`, with a default English value of "Buy my stuff!" Txbr uses this key and default value to construct the translation file it will submit to Transifex. Providing a default value allows for easy template construction and previewing, since your template probably won't be translated immediately. Braze will fall back to this value if the translation doesn't yet exist. Liquid tags that do not specify a default value will not be included in the submission to Transifex. Finally, pay close attention to the `strings.` prefix. It corresponds to the `connected_content` tag's `:save strings` option. The `:save` option tells Braze to store the translated strings in a template variable called `strings`, which can then be used to grab individual strings. The value given to `:save` must be the same value used as the key prefix. For example, simply typing `{{header.title}}` won't work.
35
+
36
+ ### Enabling Translation
37
+
38
+ Template translation is enabled by default. To skip translating a given template, add the following Liquid tag to the top of your template:
39
+
40
+ ```liquid
41
+ {% assign translation_enabled = false %}
42
+ ```
43
+
44
+ Configuration
45
+ ---
46
+
47
+ Txbr requires several configuration options in order to communicate with Braze and Transifex. Configuration is done in the YAML file format. Here's an example:
48
+
49
+ ```yaml
50
+ projects:
51
+ - handler_id: email-templates
52
+ transifex_api_username: tx_username
53
+ transifex_api_password: tx_password
54
+ strings_format: YML
55
+ source_lang: en
56
+ braze_email_address: login@yourcompany.com
57
+ braze_password: your_braze_password
58
+ braze_app_group_id: your_braze_app_group_id
59
+ braze_api_url: https://dashboard-03.braze.com/
60
+
61
+ ```
62
+
63
+ 1. The `handler_id` indicates what kind of content this project should contain. In this case, we're translating email templates, the only currently supported option.
64
+ 2. Your Transifex username and password should have access to the Transifex projects you want to submit content to. You can configure access via Transifex's access control system.
65
+ 3. The `strings_format` option must be one of [Transifex's supported formats](https://docs.transifex.com/formats/introduction).
66
+ 4. The `source_lang` option should be the language in which your source strings are written in. In other words, it should be the language in which the `default:` text is written in your template's Liquid tags.
67
+
68
+ ### Using Configuration
69
+
70
+ Txbr supports two different ways of accessing configuration, raw text and a file path. In both cases, config is passed via the `TXBR_CONFIG` environment variable. Prefix the raw text or file path with the appropriate scheme, `raw://` or `file://`, to indicate which strategy Txbr should use.
71
+
72
+ #### Raw Config
73
+
74
+ Passing raw config to Txbr can be done like this:
75
+
76
+ ```bash
77
+ export TXBR_CONFIG="raw://big_yaml_string_here"
78
+ ```
79
+
80
+ When Txbr starts up, it will use the YAML payload that starts after `raw://`.
81
+
82
+ #### File Config
83
+
84
+ It might make more sense to store all your config in a file. Pass the path to Txbr like this:
85
+
86
+ ```bash
87
+ export TXBR_CONFIG="file://path/to/config.yml"
88
+ ```
89
+
90
+ When Txbr runs, it will read and parse the file at the path that comes after `file://`.
91
+
92
+ Usage
93
+ ---
94
+
95
+ Txbr is both a library and a server. It provides access to Transifex resources via a single API endpoint, `strings.json`, and includes a set of rake tasks to extract strings from templates and upload them to Transifex.
96
+
97
+ ### API Endpoint
98
+
99
+ Txbr provides a single API endpoint for retrieving translated content from Transifex. You'll need to stand up a Txbr server somewhere and make it publicly available on the Internet. The URL to your server will be used in the `connected_content` tag in your Braze templates (see above).
100
+
101
+ The endpoint will be available at http://your_txbr_server.com/strings.json and accepts the following required GET parameters:
102
+
103
+ 1. **project_slug**: The Transifex project slug in which the resource resides.
104
+ 2. **resource_slug**: The Transifex resource containing the translated content.
105
+ 3. **locale**: The locale (i.e. language) to fetch translations for.
106
+ 4. **strings_format**: The Transifex-supported strings format the resource was created with. In our examples, we have used "YML".
107
+
108
+ The easiest way to get
109
+
110
+ ### Rake Tasks
111
+
112
+ First, load the rake task via `require txbr/tasks`. Then run `rake txbr:upload_all`. You can also install the gem and use the provided (very simple) CLI tool: `txbr upload_all`.
113
+
114
+ Running Tests
115
+ ---
116
+
117
+ Txbr uses the popular RSpec test framework and has a comprehensive set of unit tests. To run the test suite, run `bundle exec rspec`.
118
+
119
+ Requirements
120
+ ---
121
+
122
+ Txbr requires an Internet connection to access the Transifex and Braze APIs.
123
+
124
+ Compatibility
125
+ ---
126
+
127
+ Txdb requires Ruby 2.5.
128
+
129
+ Authors
130
+ ---
131
+
132
+ This project is maintained by [Cameron Dutro](https://github.com/camertron).
133
+
134
+ License
135
+ ---
136
+
137
+ Licensed under the Apache License, Version 2.0. See the LICENSE file included in this repository for the full text.
@@ -0,0 +1,81 @@
1
+ require 'liquid'
2
+
3
+ module Txbr
4
+ autoload :Application, 'txbr/application'
5
+ autoload :BrazeApi, 'txbr/braze_api'
6
+ autoload :BrazeSession, 'txbr/braze_session'
7
+ autoload :BrazeSessionApi, 'txbr/braze_session_api'
8
+ autoload :Commands, 'txbr/commands'
9
+ autoload :Config, 'txbr/config'
10
+ autoload :EmailTemplate, 'txbr/email_template'
11
+ autoload :EmailTemplateComponent, 'txbr/email_template_component'
12
+ autoload :EmailTemplateHandler, 'txbr/email_template_handler'
13
+ autoload :Project, 'txbr/project'
14
+ autoload :RequestMethods, 'txbr/request_methods'
15
+ autoload :StringsManifest, 'txbr/strings_manifest'
16
+ autoload :Uploader, 'txbr/uploader'
17
+ autoload :Utils, 'txbr/utils'
18
+
19
+ class BrazeApiError < StandardError
20
+ attr_reader :status_code
21
+
22
+ def initialize(message, status_code)
23
+ super(message)
24
+ @status_code = status_code
25
+ end
26
+ end
27
+
28
+ class BrazeUnauthorizedError < BrazeApiError
29
+ def initialize(message)
30
+ super(message, 401)
31
+ end
32
+ end
33
+
34
+ class BrazeNotFoundError < BrazeApiError
35
+ def initialize(message)
36
+ super(message, 404)
37
+ end
38
+ end
39
+
40
+ class << self
41
+ def handler_for(project)
42
+ handlers[project.handler_id].new(project)
43
+ end
44
+
45
+ def register_handler(id, klass)
46
+ handlers[id] = klass
47
+ end
48
+
49
+ private
50
+
51
+ def handlers
52
+ @handlers ||= {}
53
+ end
54
+ end
55
+
56
+ Txbr.register_handler('email-templates', Txbr::EmailTemplateHandler)
57
+
58
+
59
+ class ConnectedContentTag < Liquid::Tag
60
+ # This is a regular expression to pull out the variable in
61
+ # which to store the value returned from the call made by
62
+ # the connected_content filter. For example, if
63
+ # connected_content makes a request to http://foo.com and is
64
+ # told to store the results in a variable called "strings",
65
+ # the API response will then be accessible via the normal
66
+ # Liquid variable mechanism, i.e. {{...}}. Say the API at
67
+ # foo.com returned something like {"bar":"baz"}, then the
68
+ # template might contain {{strings.bar}}, which would print
69
+ # out "baz".
70
+ PREFIX_RE = /:save\s+(#{Liquid::Lexer::IDENTIFIER})/
71
+
72
+ attr_reader :tag_name, :prefix
73
+
74
+ def initialize(tag_name, arg, *)
75
+ @tag_name = tag_name
76
+ @prefix = arg.match(PREFIX_RE).captures.first
77
+ end
78
+ end
79
+
80
+ Liquid::Template.register_tag(:connected_content, ConnectedContentTag)
81
+ end
@@ -0,0 +1,48 @@
1
+ require 'abroad'
2
+ require 'json'
3
+ require 'sinatra/json'
4
+ require 'txgh'
5
+
6
+ module Txbr
7
+ class Application < Sinatra::Base
8
+ TARGET_FORMAT = 'json/dotted-key'.freeze
9
+ REQUIRED_PARAMS = %w(project_slug resource_slug locale strings_format).freeze
10
+
11
+ get '/strings.json' do
12
+ begin
13
+ REQUIRED_PARAMS.each do |required_param|
14
+ unless params.include?(required_param)
15
+ status 400
16
+ return json(error: "Missing parameter '#{required_param}'")
17
+ end
18
+ end
19
+
20
+ transifex_client = Txgh::TransifexApi.create_from_credentials(
21
+ Txbr::Config.transifex_api_username,
22
+ Txbr::Config.transifex_api_password
23
+ )
24
+
25
+ source = transifex_client.download(
26
+ params[:project_slug], params[:resource_slug], params[:locale]
27
+ )
28
+
29
+ target = StringIO.new
30
+ strings_format = Txgh::ResourceContents::EXTRACTOR_MAP[params[:strings_format]]
31
+
32
+ Abroad.serializer(TARGET_FORMAT).from_stream(target, params[:locale]) do |serializer|
33
+ Abroad.extractor(strings_format)
34
+ .from_string(source)
35
+ .extract_each do |key, value|
36
+ serializer.write_key_value(key, value)
37
+ end
38
+ end
39
+
40
+ status 200
41
+ json(JSON.parse(target.string))
42
+ rescue StandardError => e
43
+ status 500
44
+ json(error: e.message)
45
+ end
46
+ end
47
+ end
48
+ end