Closed Aadjou closed 7 years ago
@AVGP I like to have your insight on this. I thought, if the repository will go public anyways, we might not need a deployment for this. So the processing-server can directly pull the source from github from the respective branch. Else I could setup a jenkins job that deploys a zip on s3. What do you think?
I agree. Github has a builtin way to get a ZIP of this repository. This ZIP is available via a URL anyway, so we'd duplicate an existing Github feature for no good reason that I could see :-)
And if we don't want processing server to pull the zip, yes, there's the so-called "raw URLs" on github that give, well, raw access to the files via HTTPS
There will be official Github releases which can be downloaded via HTTP
https://github.com/archilogic-com/data3d-blender-io/releases
ZIP or Tar:
github.com/archilogic-com/data3d-blender-io/archive/version-name.zip or .tar.gz
Create deployment for blender addonChange addon name reference in spacesRemove addon from spaces repository