-
-
Notifications
You must be signed in to change notification settings - Fork 680
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
Article on how are we using Digital Ocean at AsyncAPI #927
Comments
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Still relevant |
Hello @derberg |
@BhaswatiRoy that would be awesome, but we first need @smoya to provide technical input for the article |
Sure @derberg |
Hi @BhaswatiRoy! Im on parental leave, so I'm gonna give my best. We do use Digital Ocean for some things, such as hosting the AsyncAPI Event Gateway, hosting the Server-API, and the Studio. The first two are deployed into a K8s cluster managed by Digital Ocean. The deployment of those projects are made with Helm, files available under The K8s cluster is created through Terraform and the files are located under https://github.com/asyncapi/infra. Hope this helps! |
Should the article contain in depth about how we use digital ocean or just an overview of it? |
@derberg Is someone still working on this issue? |
nobody is working on it |
Sure I will complete the others, then take this up if it's still free. |
@Shurtu-gal are you working on this? |
Not currently, you can take it up but recently we are shifting from k8s to apps. @smoya can point it out better. |
Folks, what's the update on the article here?😄 Is someone working on it? If yes, progress please? |
No one is working on it |
@sambhavgupta0705 This is a BLOG post, not a doc. Do not spam the docs channel with blog post requests. |
Btw, the only thing hosted in Digital Ocean at this time is the Server-API. The infrastructure is managed by this Terraform file and the app is deployed on each merge to |
Is this still needed @derberg ? |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
I think we don't require this now so I am closing this one |
Post title
Hosting community services on Kubernetes with Digital Ocean
Post description
This article needs 2 sections:
$1200
that will secure our deployments for a few months. So support of DO continues since it started last year.@smoya sending some 🍻 and ❤️ towards you to encourage you to write this article 😄
The text was updated successfully, but these errors were encountered: