Skip to content

Fix formatting of approved user message template #2373

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

Merged
merged 1 commit into from
May 23, 2025

Conversation

kabilar
Copy link
Member

@kabilar kabilar commented May 13, 2025

Since the current template results in the following message:

image

@yarikoptic yarikoptic added the patch Increment the patch version when merged label May 23, 2025
@@ -1,8 +1,7 @@
{% autoescape off %}
Dear {{ greeting_name }},

Your DANDI account has been approved. You can go to {{ dandi_web_app_url }} and login with your GitHub account
to start creating dandisets and uploading data.
Your DANDI account has been approved. You can go to {{ dandi_web_app_url }} and login with your GitHub account to start creating dandisets and uploading data.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note @NEStock : do you have vendorization patch for this by any chance? ;-)

Copy link
Contributor

@NEStock NEStock May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yarikoptic we replaced instances of the text "DANDI" with "EMBER-DANDI" by hand.

And then dandi_web_app_url is set in dandi-infrastructure, so we were able to change that easily (https://github.com/aplbrain/dandi-infrastructure/blob/f8c0f4b437aa0fcb6beee9d75602e8cae49f2c32/terraform/api.tf#L47)

Here is the EMBER version of this file for reference: https://github.com/aplbrain/dandi-archive/blob/527b818a664e1a4c8878b1131699ff5ec7376097/dandiapi/api/templates/api/mail/approved_user_message.txt#L4

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should review/decide on what is the best way to organize such elements for "vendorization"... I guess we should aim by default to propagate all the config variables in here but allow for a complete overload of the messages happen a particular archive needs more specific customization...

@yarikoptic yarikoptic merged commit 5874e69 into dandi:master May 23, 2025
9 of 11 checks passed
@dandibot
Copy link
Member

dandibot commented Jun 4, 2025

🚀 PR was released in v0.11.0 🚀

@dandibot dandibot added the released This issue/pull request has been released. label Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Increment the patch version when merged released This issue/pull request has been released.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants