-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add blog posts about Binder federation member and docker stacks #356
Conversation
Co-authored-by: Yuvi Panda <[email protected]>
I've updated the post to focus more on the single-node workflow rather than one specific cloud provider. I think the post should be ready to go whenever @yuvipanda thinks it's OK. |
Things to add if you so desire:
|
@yuvipanda do you have any objection to me incorporating a quick round of feedback and then posting this on Monday? |
@choldgraf if you incorporate #356 (comment) you can post it on monday! don't need to wait for me |
Woot ok that's my plan then |
Do you have a link to a pr where we added that object storage functionality? |
@choldgraf ok, I actually take this back, I want to change this a little now that I've added another member. So hang on. |
Is the image duplicated? |
Thanks everybody for the feedback. I incorporate some of the "landscape changes" that @yuvipanda mentioned, as well as the suggestions and edits from others. I also reframed this to be a bit more confident - I think that we can say this "experiment" is working and that we're already "in production" with this instance, so I've been clearer about this as well as the big picture of what this means. I think this is ready to go from my perspective. Let me know if others have objections to posting it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job love it @choldgraf!
OK one more small change to the pricing after some better links from @yuvipanda and I think we're good to go. Thanks all for the feedback and iteration on this! |
This provides two draft blog posts to describe upstream impact that 2i2c has been involved with.
If either of these is controversial we can split this into 2 PRs but I thought it'd be easy-enough to add a quick stub post about Docker Stacks first.