-
Notifications
You must be signed in to change notification settings - Fork 0
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
ATLA staging deployment & actions #1
Comments
Noting that there are a few flapping rspec tests and some lint error after setting up CI. |
Tested and passed items 1 - 8 & 13 screenshots below demo proprietor: atla-hyku.notch8.cloud |
After troubleshooting the issue on staging with google analytics I found the issue and solution; I have added the solution to this repository and also contributed back to hyku in pr here: samvera/hyku#1937 |
NICE job figuring this one out April!! 🥳 |
QA in progress: Testing instructions
|
This passes SoftServ QA: See attached screenshots. tested on:
|
I added a demo in the body of the ticket that shows you how to complete the following steps:
|
The questions below are from a while ago when this ticket was put up for me to review, i have not tried again on any of it The testing steps
Questions
|
&&
this is an issue in hyku/hyrax upstream. Currently, work is being done in PALs for analytics, but we may want to hold off on turning on analytics in production until it is contributed back, since the numbers are a bit off.
sentry is just on our end for error tracking, don't worry about testing it
no, it should not send an actual email at this point. From staging, the emails will go to mailtrap so actual emails can't be accidentally spammed while testing on the staging site. Here is a screenshot of the email that i see in mailtrap to confirm that it is actually working. On prod, its configured to send to the real email vs. to the mailtrap inbox.
Negative Captcha not working #19 addresses this issue |
Thank you ! this all makes sense to me. turning it off for now sounds like the way to go. Can we maybe make a ticket to remember to come back to it once it has been contributed back? |
Summary
Staging is on r2-staging cluster on SoftServ infrastructure for now per Rob's request.
ATLA wants a new multi tenant hyku instance. This application will need both a staging and a production instance. Resources like Fedora that can be share should be shared. The environment variables should be set up to incorporate with other systems, like sentry, etc.
Acceptance criteria
provided client admin user credentials: https://start.1password.com/open/i?a=LTLZ652TT5H5FHMYMASSH7PIXM&v=yzbdi74r4kytavonu7pq4323aa&i=e5cb5ywp7zgwjnw4o7mo7yyxsa&h=scientist.1password.com
initial admin seeded user credentials: https://start.1password.com/open/i?a=LTLZ652TT5H5FHMYMASSH7PIXM&v=huuakin4bu4xanlhktv42qheam&i=tyuxk2mpicalb4lljw7zcmbcei&h=scientist.1password.com
initial non-admin seeded user credentials: https://start.1password.com/open/i?a=LTLZ652TT5H5FHMYMASSH7PIXM&v=huuakin4bu4xanlhktv42qheam&i=ics4ramxhzb6hkp4p6il665mvm&h=scientist.1password.com
Testing instructions
--------if you get to here and have checked all the above items and they have passed, this ticket passes. Please continue testing, but if anything does not work, please make a ticket for it and ref this ticket please.
when you navigate to the tenants contact us page you are able to submit a form and look in mailtrap and see the email -- Note April 14,2023, form April: Negative captcha is blocking testing on this on the contact us page, is there another way to test email sending?Dashboard
>Manage Users
your-tenant-name.atla-hyku.notch8.cloud/admin/analytics/collection_reports
your-tenant-name.atla-hyku.notch8.cloud/admin/analytics/work_reports
Analytics
Demo: How to log in and create a tenant
Screen.Recording.2023-04-25.at.03.14.35.PM.mp4
Basic auth for staging only:
![Sign in 2023-04-25 at 3 18 18 PM](https://user-images.githubusercontent.com/29311858/234416567-89802a30-cdb3-4df8-9f93-32a2ea718cee.jpg)
Username:
samvera
Password:
hyku
The text was updated successfully, but these errors were encountered: