-
Notifications
You must be signed in to change notification settings - Fork 146
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
Link to Gluon book in README.md 404s #881
Comments
The whole site is down for me |
Same here, the whole site is down for me too. |
@Marwes How about separating the playground and static document? Using reverse proxy provided by Nginx or Caddy can easily do this. So when the playground crashes, users can still read the document. |
I think this is due to a bug in the interaction between futures and IO actions which causes the server to go down. So separating the playground and the rest of the server may not help since the server itself uses gluon. The short term fix, I think, is to setup up a supervisor for the server which restarts it when it crashes. Then the bug with IO actiosn just needs to fixed. |
Currently there is just lonely EC2 instance + cron script which tries to keep the server up and running. This isn't great as I need to ssh in to look at logs and the service only restarts once per day. By moving to ECS we get logs in cloudwatch, automatic restarts on crashes and we can setup alarms for any error cases. (Terraform is certainly overkill for this, but setting up a new terraform environment is good for learning, I already have a decent understanding of maintaining one so). cc gluon-lang/gluon#881
Currently there is just lonely EC2 instance + cron script which tries to keep the server up and running. This isn't great as I need to ssh in to look at logs and the service only restarts once per day. By moving to ECS we get logs in cloudwatch, automatic restarts on crashes and we can setup alarms for any error cases. (Terraform is certainly overkill for this, but setting up a new terraform environment is good for learning, I already have a decent understanding of maintaining one so). cc gluon-lang/gluon#881
Currently there is just lonely EC2 instance + cron script which tries to keep the server up and running. This isn't great as I need to ssh in to look at logs and the service only restarts once per day. By moving to ECS we get logs in cloudwatch, automatic restarts on crashes and we can setup alarms for any error cases. (Terraform is certainly overkill for this, but setting up a new terraform environment is good for learning, I already have a decent understanding of maintaining one so). cc gluon-lang/gluon#881
There is a broken link in the Documentation section of the github README. The correct link is https://gluon-lang.org/doc/crates_io/book/index.html
The text was updated successfully, but these errors were encountered: