This is usually easier within a JS/TS environment, however I know it's possible with Rust.
We need to build a full list of dependencies and how to install them, and then create a simple method to build a new Docker image that contains all these dependencies. Then, we likely need another file that works on building the actual server application with the correct addressing.
We most likely want to start with the rust:1.90 Docker image - at the time of writing, this is the most up-to-date version of Rust. We want to keep it as lightweight as possible. Manual setup of this image is ok as well - sometimes nvm or fnm (user preference) don't work the way we expect them to.
This is usually easier within a JS/TS environment, however I know it's possible with Rust.
We need to build a full list of dependencies and how to install them, and then create a simple method to build a new Docker image that contains all these dependencies. Then, we likely need another file that works on building the actual server application with the correct addressing.
We most likely want to start with the `rust:1.90` Docker image - at the time of writing, this is the most up-to-date version of Rust. We want to keep it as lightweight as possible. Manual setup of this image is ok as well - sometimes `nvm` or `fnm` (user preference) don't work the way we expect them to.
Dockerfiles were ironed out as part of #27, however there are still improvements that can be made.
I want to create a real pipeline for this that will build the docker image as part of a Github Action, push it to AWS ECR, and then pull the image on the EC2 instance.
Dockerfiles were ironed out as part of #27, however there are still improvements that can be made.
I want to create a real pipeline for this that will build the docker image as part of a Github Action, push it to AWS ECR, and then pull the image on the EC2 instance.
It's possible that hosting this on AWS isn't the best way to work with it, since we do most of our work through Github Actions. Actions are free for longer than AWS offers, and so hosting the Docker image on Github's public Docker repo might not be a horrible idea. If we really (really) want to keep using a private AWS ECR instance, then we can do that, but using ghcr.io may not be a bad plan.
It's possible that hosting this on AWS isn't the best way to work with it, since we do most of our work through Github Actions. Actions are free for longer than AWS offers, and so hosting the Docker image on Github's public Docker repo might not be a horrible idea. If we really (really) want to keep using a private AWS ECR instance, then we can do that, but using `ghcr.io` may not be a bad plan.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This is usually easier within a JS/TS environment, however I know it's possible with Rust.
We need to build a full list of dependencies and how to install them, and then create a simple method to build a new Docker image that contains all these dependencies. Then, we likely need another file that works on building the actual server application with the correct addressing.
We most likely want to start with the
rust:1.90Docker image - at the time of writing, this is the most up-to-date version of Rust. We want to keep it as lightweight as possible. Manual setup of this image is ok as well - sometimesnvmorfnm(user preference) don't work the way we expect them to.Dockerfiles were ironed out as part of #27, however there are still improvements that can be made.
I want to create a real pipeline for this that will build the docker image as part of a Github Action, push it to AWS ECR, and then pull the image on the EC2 instance.
It's possible that hosting this on AWS isn't the best way to work with it, since we do most of our work through Github Actions. Actions are free for longer than AWS offers, and so hosting the Docker image on Github's public Docker repo might not be a horrible idea. If we really (really) want to keep using a private AWS ECR instance, then we can do that, but using
ghcr.iomay not be a bad plan.An automated system using Github Actions was implemented as part of #37 and #38. Closing this issue.