rust-lang / rust-lang/rust-playground
Deployment Information
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
Hey there!
We are working on a fork of this repository geared toward running Java code/tools instead of rust ones here
There are deployment steps in the repo, but we were wondering if there is anything we should be aware of (like, what instance size to use, steps to get the ec2 machine working to serve our domain name, etc.) or anything else that isn't documented or has been learned running the rust playground in production for however many years.
Thank you for your time
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository's existing deployment steps and compare them with the unanswered questions in this issue. Determine what production guidance can be documented for EC2 instance sizing, serving the domain, and lessons from running the Rust Playground; done means those deployment considerations are written down for the Java fork.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, rust
- Domain
- cloud, devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100