You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can also run the import and export tasks programmatically from your code. To achieve that, please check the [`lokalise_manager`](https://github.com/bodrovis/lokalise_manager) gem which `lokalise_rails` relies on.
@@ -217,76 +287,6 @@ end
217
287
218
288
Named projects are configured with `for_project(:name)` and generate scoped tasks like `lokalise_rails:<name>:import` and `lokalise_rails:<name>:export`.
219
289
220
-
## Configuration
221
-
222
-
Options are specified in the `config/lokalise_rails.rb` file.
223
-
224
-
Here's an example:
225
-
226
-
```ruby
227
-
LokaliseRails::GlobalConfig.config do |c|
228
-
# These are mandatory options that you must set before running rake tasks:
229
-
c.api_token =ENV['LOKALISE_API_TOKEN']
230
-
c.project_id =ENV['LOKALISE_PROJECT_ID']
231
-
232
-
# Provide a custom path to the directory with your translation files:
233
-
# c.locales_path = "#{Rails.root}/config/locales"
234
-
235
-
# Provide a Lokalise project branch to use:
236
-
c.branch ='develop'
237
-
238
-
# Provide request timeouts for the Lokalise API client:
1. Copy-paste `.env.example` file as `.env`. Put your Lokalise API token and project ID inside. The `.env` file is excluded from version control so your data is safe. All in all, we use stubbed requests, so the actual API requests won't be sent. However, providing at least some values is required.
0 commit comments