When installling on a directory-level, I got this error.

I think you can reproduce it like this:

mkdir test;
cd test;
composer require openl10n/cli;
vendor/openl10n/cli/bin/openl10n init;

The pull command does not work either when in a openl10n-managed directory

The command is unable to detect language files when they are at the root of the project.

For instance: https://git.popcorntime.io/stash/projects/pt/repos/popcorn-i18n/browse

server: dev
project: popcorn-i18n
files:
    - <locale>.json

Example of conf file:

server: openl10n.dev
project: demo
files:
    expr: src/Openl10n/Bundle/*/Resources/translations/<domain>.<locale>.*
    export_to: app/Resources/translations/<domain>.<locale>.xlf

See

• 2372acc
• https://github.com/openl10n/openl10n/blob/master/src/Openl10n/Domain/Resource/Application/Action/ImportTranslationFileAction.php#L10
• https://github.com/openl10n/openl10n/blob/master/src/Openl10n/Domain/Resource/Application/Action/ExportTranslationFileAction.php#L9

files:
  - 
    pattern: path/to/<locale>.yml
    # File set specific options
    options: 
       push: [reviewed, erase, clean]
       pull: [reviewed, fallback_locale, fallback_key]

# Global options
options:
  push: [reviewed, erase, clean]
  pull: [reviewed, fallback_locale, fallback_key]

Like https://getcomposer.org/doc/00-intro.md#installation-nix

Would you mind if we add unit test or spec on the project ?
Which would have your preference ? I've noticed that https://github.com/openl10n/openl10n use specs

Allow recursive glob pattern (**) when finding files.
Example for a Symfony project:

src/**/*Bundle/Resources/translations/*.<locale>.yml

Example of configuration file

server:
    host: openl10n.local
    login: user
    password: user

project: foobar

files:
    expr: 
        - src/Acme/Bundle/*/Resources/translations/<domain>.<local>.*
        - strings/<locale>/LC_MESSAGES/<domain>.*
    exclude: messages.en.yml

options: ~

Or specify credentials in user's home directory (~/.openl10n.yml):

hosts:
    openl10n.dev:
        user: user
        password: user
        #use_ssl: true

Then only use:

server: openl10n.dev

to validate current config file

Hi!

I get the following error when I'm building the phar:

  [RuntimeException]
  The file "/Users/someuser/Work/tools/openl10n-cli/vendor/guzzlehttp/guzzle/src/cacert.pem" does not exist or is not a file.

Box version:

Box version 2.6.1 build c9ee902145324690459664bd938ed31475d58347

For instance:

files:
  - path/to/translations/<context>.<locale>.xliff

Depends on openl10n/openl10n#89.

Rename config file to .openl10n.yml, to be coherent with other system configuration (eg. .travis.yml, .scrutinizer.yml, .php_cs)

This fails:

openl10n init http://user:[email protected] silex --no-interaction

TODO:

• initialize(): init conf in memory from $input + file (if exists)
• interact(): ask for missing conf
• execute(): validate conf + write into file if in memory conf is different

First of all thanks a lot for this awesome project. I've been thinking about something like openl10n for a long time.

As openl10n.phar allow to push a specific file, I think that it make sense to be able to pull a specific file / folder.
We have been able to bypass this by creating various configuration files. But it's not really reliable.

If you validate this feature, we will try to implement it. :)

Hi,

It would be nice if we could filter some files to push (and/or pull), because the upload may be slow.

If you know that you have modified only one file, you do not want to push all files. This way, we can develop post-commit hooks or something like that.

I started to dive into the push code friday, but how do you see that:

• Does it needs to be in the sdk (I don't know why but it can be usefull to filter your resources):
  • pro: will work on all potential client
  • con: I think it will not work if you add a new file
• or just in the cli command

Tell me how you see it and I will push you some code.

Thanks
Julien

https://travis-ci.org/openl10n/openl10n-cli/jobs/90368179
Something often went wrong on travis, always with this step features/cli/push.feature:145
I haven't been able to reproduce it locally either with php 5.5 or 5.6

See http://moquet.net/blog/distributing-php-cli/

Add rules to detect file patterns automatically.

For instance, in a Symfony2 app, find files under pattern src/**/*Bundle/Resources/translations/*, and if matching, suggest default patterns on init command.