-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the S3 file structure #22
Comments
The directory structure should be compatible with the update plugin out of the box. The paths are defined (and overridable in The update plugin will also use these same paths so you can have any structure you like. Yes, this should be documented but I'm not sure the best place for it. I feel adding it to the release section of the docs would be adding too much detail. |
Also, the Heroku CLI uses these defaults so you should be getting exactly the same thing. |
Thanks for the prompt response. How would one define a channel when running |
you set the version to something like |
Well that makes a lot of sense. I guess I was just overthinking it based on the Heroku CLI scripts. |
Still, I don't think this is documented anywhere. I'll see if I can add that somewhere |
thoughts? oclif/oclif.github.io@829f4ed |
That looks great. I would suggest noting that the version change occurs in the package.json file (as opposed to, say, a command line flag). |
fix: add success msg + fix tar ext
Pardon me if this plugin is not ready for public consumption...
As far as I can tell,
dev pack
alone does not produce the correct directory structure to sync with S3. The Heroku CLI does some extra magic to add channel folders. What is the proper way to make the magic happen? Ideally I supposepack
/publish
should incorporate channels (somehow?), but I was hoping for an expert take on the roadmap here.The text was updated successfully, but these errors were encountered: