Re: [Weblate] git push invalid auth

2018-04-07 Thread Michal Čihař
Hi

There will be always one commit per author.

See docs for inromation how Weblate commits:

https://docs.weblate.org/en/latest/admin/continuous.html#lazy-commits

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/


On Fri, 2018-04-06 at 16:44 +, bruno.darrig...@orange.com wrote:
> Ok thanks, Michal,
> 
> Now it works, but it works too fine :-),  is there an option
> somewhere to merge several modifications in only one commit (only
> when we push to gitlab) ? (instead of 1 commit per update)
> 
> Thks
> Bruno
> 
> 
> 
> 
> -Message d'origine-
> De : Weblate [mailto:weblate-bounces+bruno.darrigues=orange.com@lists
> .cihar.com] De la part de Michal Cihar
> Envoyé : vendredi 6 avril 2018 16:58
> À : weblate@lists.cihar.com
> Objet : Re: [Weblate] git push invalid auth
> 
> Hello
> 
> For https, the example with token should work, see https://docs.webla
> te.org/en/latest/vcs.html#https-repositories
> 
> For git, you need to use keys, see our docs:
> 
> https://docs.weblate.org/en/latest/vcs.html#ssh-repositories
> 
> The SOCIAL_AUTH_* fields are for authentication of users in Weblate.
> 
> -- 
>   Michal Čihař | https://cihar.com/ | https://weblate.org/
> 
> 
> 
> bruno.darrig...@orange.com píše v Út 27. 03. 2018 v 10:56 +:
> > Hi
> >  
> > I use weblate in an local docker service but i have an issue when
> > push 
> > updates to my github repo.
> > I already tried  différents url in push repo url :
> > https://user:pasw...@github.com/brusand/project.git
> > https://user:to...@github.com/brusand/project.git
> > git:user:pasw...@github.com/brusand/project.git
> > git:user:to...@github.com/brusand/project.git
> > SOCIAL_AUTH_GITHUB_KEY
> > SOCIAL_AUTH_GITHUB_SECRET
> >  
> > May I missed something ? (I use git to push updates outside of
> > weblate 
> > and works fine) Have you some samples ?
> >  
> > Best regards
> > Bruno
> >  
> >  
> > ___
> > __
> > 
> > 
> > Ce message et ses pieces jointes peuvent contenir des informations 
> > confidentielles ou privilegiees et ne doivent donc pas etre
> > diffuses, 
> > exploites ou copies sans autorisation. Si vous avez recu ce
> > message 
> > par erreur, veuillez le signaler a l'expediteur et le detruire
> > ainsi 
> > que les pieces jointes. Les messages electroniques etant
> > susceptibles 
> > d'alteration, Orange decline toute responsabilite si ce message a
> > ete 
> > altere, deforme ou falsifie. Merci.
> > 
> > This message and its attachments may contain confidential or 
> > privileged information that may be protected by law; they should
> > not 
> > be distributed, used or copied without authorisation.
> > If you have received this email in error, please notify the sender
> > and 
> > delete this message and its attachments.
> > As emails may be altered, Orange is not liable for messages that
> > have 
> > been modified, changed or falsified.
> > Thank you.
> > ___
> > Weblate mailing list
> > Weblate@lists.cihar.com
> > https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
> 
> _
> 
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous
> avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere,
> deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or
> privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender
> and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have
> been modified, changed or falsified.
> Thank you.
> 


signature.asc
Description: This is a digitally signed message part
___
Weblate mailing list
Weblate@lists.cihar.com
https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate


Re: [Weblate] git push invalid auth

2018-04-06 Thread bruno.darrigues
Ok thanks, Michal,

Now it works, but it works too fine :-),  is there an option somewhere to merge 
several modifications in only one commit (only when we push to gitlab) ? 
(instead of 1 commit per update)

Thks
Bruno




-Message d'origine-
De : Weblate 
[mailto:weblate-bounces+bruno.darrigues=orange@lists.cihar.com] De la part 
de Michal Cihar
Envoyé : vendredi 6 avril 2018 16:58
À : weblate@lists.cihar.com
Objet : Re: [Weblate] git push invalid auth

Hello

For https, the example with token should work, see 
https://docs.weblate.org/en/latest/vcs.html#https-repositories

For git, you need to use keys, see our docs:

https://docs.weblate.org/en/latest/vcs.html#ssh-repositories

The SOCIAL_AUTH_* fields are for authentication of users in Weblate.

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/



bruno.darrig...@orange.com píše v Út 27. 03. 2018 v 10:56 +:
> Hi
>  
> I use weblate in an local docker service but i have an issue when push 
> updates to my github repo.
> I already tried  différents url in push repo url :
> https://user:pasw...@github.com/brusand/project.git
> https://user:to...@github.com/brusand/project.git
> git:user:pasw...@github.com/brusand/project.git
> git:user:to...@github.com/brusand/project.git
> SOCIAL_AUTH_GITHUB_KEY
> SOCIAL_AUTH_GITHUB_SECRET
>  
> May I missed something ? (I use git to push updates outside of weblate 
> and works fine) Have you some samples ?
>  
> Best regards
> Bruno
>  
>  
> _
> 
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
> exploites ou copies sans autorisation. Si vous avez recu ce message 
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi 
> que les pieces jointes. Les messages electroniques etant susceptibles 
> d'alteration, Orange decline toute responsabilite si ce message a ete 
> altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or 
> privileged information that may be protected by law; they should not 
> be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
> Thank you.
> ___
> Weblate mailing list
> Weblate@lists.cihar.com
> https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
Weblate mailing list
Weblate@lists.cihar.com
https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate


Re: [Weblate] git push invalid auth

2018-04-06 Thread Michal Čihař
Hello

For https, the example with token should work, see
https://docs.weblate.org/en/latest/vcs.html#https-repositories

For git, you need to use keys, see our docs:

https://docs.weblate.org/en/latest/vcs.html#ssh-repositories

The SOCIAL_AUTH_* fields are for authentication of users in Weblate.

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/



bruno.darrig...@orange.com píše v Út 27. 03. 2018 v 10:56 +:
> Hi
>  
> I use weblate in an local docker service but i have an issue when
> push updates to my github repo.
> I already tried  différents url in push repo url :
> https://user:pasw...@github.com/brusand/project.git
> https://user:to...@github.com/brusand/project.git
> git:user:pasw...@github.com/brusand/project.git
> git:user:to...@github.com/brusand/project.git
> SOCIAL_AUTH_GITHUB_KEY
> SOCIAL_AUTH_GITHUB_SECRET
>  
> May I missed something ? (I use git to push updates outside of
> weblate and works fine)
> Have you some samples ?
>  
> Best regards
> Bruno
>  
>  
> _
> 
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous
> avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere,
> deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or
> privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender
> and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have
> been modified, changed or falsified.
> Thank you.
> ___
> Weblate mailing list
> Weblate@lists.cihar.com
> https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate


signature.asc
Description: This is a digitally signed message part
___
Weblate mailing list
Weblate@lists.cihar.com
https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate