Skip to content
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

Setup bcl-up in the cloud #8

Open
sk274 opened this issue Feb 25, 2025 · 3 comments
Open

Setup bcl-up in the cloud #8

sk274 opened this issue Feb 25, 2025 · 3 comments
Assignees

Comments

@sk274
Copy link
Contributor

sk274 commented Feb 25, 2025

A ticket was created for the library systems at:

https://culibrary.atlassian.net/browse/DLITSYS-5997?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

The ECR will be named cul-it/bcl-up-prod (/int)
The ECS will be named bcl-up-prod (/int)
The S3 bucket is bcl-up

@sk274 sk274 self-assigned this Feb 25, 2025
@sk274
Copy link
Contributor Author

sk274 commented Feb 27, 2025

The library systems team created the S3 bucket, the ECR repositories, and the RDS instance.
I uploaded rails env file for each environment (prod/int/dev) to the S3 bucket and pushed image to the prod and int ECR repo's.
Greg will continue working on setting up ECS to run those images.

@sk274
Copy link
Contributor Author

sk274 commented Mar 6, 2025

The integration server is up and running.

https://bcl-up-int.library.cornell.edu

You need to be in VPN to access.

@sk274
Copy link
Contributor Author

sk274 commented Mar 7, 2025

The production instance is up and running.

https://bcl-up.library.cornell.edu

It can be accessed in the following URL as well.

https://bcl-up-prod.library.cornell.edu

For now, you need VPN to access it.
When we are ready to make the DNS switch, we should first open it up to public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant