You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
With vscode now having a remote ssh option the IDE functionality of Cloud9 is largely deprecated since most will be using the vscode progressive web app or whatever AWS editor PWA eventually gets released. I really want to stay on AWS and not spin up Github Workers and Github Codespaces on Azure.
Any way you could make the Cloud9 timeout scripts public or reference the directory they are at so I can pop a Cloud9 instance and look? I would like to have a CloudFormation script that booted an EC2 Ubuntu 20.04 with the IDE timeout scripts. If they are too tightly coupled with Cloud9 I could probably refactor to include a simple timer daemon and figure out how to trigger it via SSH use. To lower costs I would like to have two EC2s on the same EBS volume - a smaller one for day to day - and a full metal when I need a beast to compile something like Chrome.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With vscode now having a remote ssh option the IDE functionality of Cloud9 is largely deprecated since most will be using the vscode progressive web app or whatever AWS editor PWA eventually gets released. I really want to stay on AWS and not spin up Github Workers and Github Codespaces on Azure.
Any way you could make the Cloud9 timeout scripts public or reference the directory they are at so I can pop a Cloud9 instance and look? I would like to have a CloudFormation script that booted an EC2 Ubuntu 20.04 with the IDE timeout scripts. If they are too tightly coupled with Cloud9 I could probably refactor to include a simple timer daemon and figure out how to trigger it via SSH use. To lower costs I would like to have two EC2s on the same EBS volume - a smaller one for day to day - and a full metal when I need a beast to compile something like Chrome.
The text was updated successfully, but these errors were encountered: