Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Mathieu Dumont
    @Madumo
    <3
    Louis-Michel Couture
    @louim
    Hey!
    While setting up, we noticed to ENV var not mentioned in the readme. Before opening an issue, I wanted to ask about those:
    CANONICAL_HOST: seems to be only used to generate the image path in the email.
    SECRET_KEY_BASE: not mentioned in readme, I guess it should be filled, right? :grin:
    Rémi Prévost
    @remiprev
    Oh indeed! Could you open an issue for it please? :)
    Louis-Michel Couture
    @louim
    Sure!
    Louis-Michel Couture
    @louim
    Hey! I was wondering if there's a specific reason why the default merge option in accent-cli is set to passive whereas in the web interface the default seems to be smart.
    Simon Prévost
    @simonprev
    The popular choice has changed to passive recently so a merge doesn’t overwrite anything... I guess we should change it in the Ember app!
    Louis-Michel Couture
    @louim
    I'm trying to set up our first project with more than 2 languages. Here's what my accent.json looks like:
    {
      "api": {
        "url": "url",
        "key": "key"
      },
      "sync": [
        {
          "language": "en",
          "format": "rails_yml",
          "path": "config/locales/*en.yml"
        }
      ],
      "addTranslations": [
        {
          "language": "fr",
          "format": "rails_yml",
          "path": "config/locales/*fr.yml"
        },
        {
          "language": "es",
          "format": "rails_yml",
          "path": "config/locales/*es.yml"
        },
        {
          "language": "de",
          "format": "rails_yml",
          "path": "config/locales/*de.yml"
        }
      ]
    }
    however, running accent add-translations --write only run on the french language. Is this how the file is supposed to look?
    Simon Prévost
    @simonprev
    Does accent add-translations print the changes for every languages or only the french?
    Louis-Michel Couture
    @louim
    it only shows french
    Michael Rittmeister
    @DRSchlaubi
    make dev-start does always tell me to create a erlang.cookie file but i dont know how
    Michael Rittmeister
    @DRSchlaubi
    even if you create a volume for /home/accent/.erlang.cookie it doesnt work
    Michael Rittmeister
    @DRSchlaubi
    I got this thing working but now I got stuck at setting up a authentication provider I described more of this here mirego/accent#105
    Maurice Gonzenbach
    @maurice-g
    Does anyone have experience using accent with multiple branches / environments?
    Strings might no be the same on master / dev, some strings might exist in dev that don't exist in master and vice versa. Finally, dev is merged into master and the old master keys, that are not used anymore, become obsolete and should be deleted.
    Sorry if I'm missing something super-obvious here, just getting started with accent.
    Simon Prévost
    @simonprev
    Hi Maurice, There is a concept of "versions" builtin in Accent but I don’t think it works for your use case. The way syncing should work is that only your master branch should be synced with Accent. There is no concepts of mergeing two branches in Accent
    Jayce Miller
    @jicee13
    Hey @simonprev was there anything else yall were looking for in my PR? Just checking in. mirego/accent#176
    Simon Prévost
    @simonprev
    Sorry for the delay, I was just wondering why does all the file has to be in the new meta attribute? I understand the "@@" keys but not the others
    Jayce Miller
    @jicee13

    No worries. Well, the main reason I ended up putting everything in the meta was to preserve order upon export. Otherwise during serialization when I was combining the stored entries with the "@@" keys I had in the meta, the exported file wasn't guaranteed to look exactly like the imported ones because order could be different. This way I am able to preserve that by indexing everything and I make sure to overwrite any entries that may have been updated by using the value we have stored in the translations table (https://github.com/mirego/accent/pull/176/files#diff-9f71fa89815a2e9657785d5192989b7cR32).

    I'm definitely open to other suggestions though if you have a good way of handling that.

    Simon Prévost
    @simonprev
    You could store only the "@" and "@@" keys in the meta and map the matching "@" with each translations in the serializer. That would work but it is still "hacky" I think. Since the "@" seems to contain context information for each keys, the cleanest way to parse/serialize them is to include them in a new column "meta" or "context" for on translation row. The column does not exist but it could be useful for other formats. What do you think?
    Jayce Miller
    @jicee13

    So you're thinking have a meta column in both the documents and translations tables? The documents meta column will have the "@@" keys and the translations meta column will have the "@" keys?

    I guess my only concern here is how to maintain the order still of the original document if we did it that way? Doing it the way you're suggesting, how do you think we could solve for that?

    Scott
    @Fma965

    hey, i'm trying to upgrade to 1.7.0 but am getting this, any advice

    14:17:16.189 [info] Application goth exited: Goth.start(:normal, []) returned an error: shutdown: failed to start child: Goth.Config
    (EXIT) an exception was raised: (Jason.DecodeError) unexpected byte at position 0: 0x65 ('e')
    (jason 1.2.2) lib/jason.ex:78: Jason.decode!/2
    (goth 1.2.0) lib/goth/config.ex:199: Goth.Config.decode_json/1
    (goth 1.2.0) lib/goth/config.ex:66: Goth.Config.load_and_init/1
    (stdlib 3.13.2) gen_server.erl:417: :gen_server.init_it/2
    (stdlib 3.13.2) gen_server.erl:385: :gen_server.init_it/6
    (stdlib 3.13.2) proc_lib.erl:226: :proc_lib.init_p_do_apply/3

    Simon Prévost
    @simonprev
    @Fma965 The value for GOOGLE_TRANSLATIONS_SERVICE_ACCOUNT_KEY should be a JSON string that starts like this: {"type": "service_account", "project_id": "p........
    Glen Barnes
    @barnaclebarnes_twitter
    I'm having trouble adding existing translations into Accent. How do add/push up content that is already translated?