Publish results to S3

[xen]

Generated files should be saved to special place.

[davelab6]

Not sure about S3, I think git and hg repos should be supported (specifying their URL and branch)

[xen]

This ticket about what to do with results of convertion of ufo files into something else.

[davelab6]

Yep, the results should ultimately be uploaded to a git or hg repo

[xen]

You mean save to the same repo and push back? I don't get it.

That means that we need to ask for write permissions to git repos? Also that means that we will be build fonts always twice, 1st time when author make changes, second time when we push again and again get notification.

I opened this ticket just for reminder for myself. May be title is little missleading, but if you like to discuss we can. I have strong arguments agains storing binary files inside repository. Even if git generally is not so terrible bad for binary files it still bad practice and will increase repository size (git doesn't suppor download resume).

Autogenerated files can have confusing workflow. What to do if file have wrong format and convertion is failed? Delete old? How to notify that it is outdated? Other question how to force author to pull changes after every commit and in few minutes bakery commit?

So, overall questions:

• Different permissions level
• Storing autogenerated binary files is not good
• (In my opinion) broken workflow

May be, just as idea, we can offer dropbox integration and send generated file into special folder. Font author will get asyncroniously notification from dropbox desktop client and in to bother him/her and don't ruin workflow.

[davelab6]

We don't push to the original repo branch, we push to another branch, or
another repo :)

Dropbox isn't acceptable, its a proprietary service. Git can behave like
Dropbox with Sparkleshare.

[xen]

Ok, then we should offer own git hosting service, because bot pushing is
prohibited by TOS https://help.github.com/articles/github-terms-of-service.
Account terms #2, may be other places. But they definitely said it several
times that against automatic commits.

On Thu, Apr 25, 2013 at 3:30 PM, Dave Crossland notifications@github.comwrote:

We don't push to the original repo branch, we push to another branch, or
another repo :)

Dropbox isn't acceptable, its a proprietary service. Git can behave like
Dropbox with Sparkleshare.

—
Reply to this email directly or view it on GitHubhttps://github.com/xen/bakery/issues/8#issuecomment-17003755
.

Mikhail Kashkin
http://comfort.ly/
http://www.vurt.ru/

[davelab6]

Okay, good to know. However, if its not automated then it seems like any
git GUI to me.

[xen]

We are closed all questions here.