zydronium/manage.get.gov
1
0
Fork 0
mirror of https://github.com/cisagov/manage.get.gov.git synced 2025-08-14 21:44:08 +02:00
Code Issues Projects Releases Packages Wiki Activity

Fix footnote bullet points format

Browse source
This commit is contained in:
CocoByte 2024-02-28 20:14:40 -07:00
parent 54b27ef492
commit 7fa667922e
No known key found for this signature in database
GPG key ID: BBFAA2526384C97F
1 changed files with 14 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/architecture/decisions/0025-caching.md
View file

@ -56,6 +56,7 @@ We will forgo (negligible) load-time improvements by leaving caching off.
## (Footnote - How to implement caching)
Here are notes for implementing caching using whitenoise should we decide to pick this up again in the future;
1 - Add caching capability to a sandbox using the following steps (or ![following documentation for command line](https://cloud.gov/docs/services/external-domain-service/))
- Log-in to the cloud.gov website
- ![Navigate to "Services"](https://dashboard.fr.cloud.gov/services). Click "Add Service"...
@ -67,5 +68,7 @@ Here are notes for implementing caching using whitenoise should we decide to pic
Before you can continue, work with Cameron to setup the DNS in AWS (use the following documentation linked below):
https://cloud.gov/docs/services/external-domain-service/
- Once the DNS is setup, you *should* be able to continue. We did not test this.
2- Enable caching in the code with Whitenoise (see ![documentation on Whitenoise Caching](https://whitenoise.readthedocs.io/en/latest/djangohtml#add-compression-and-caching-support))
3- Take performance measurements before/after caching is enabled to determine cost-benefits of implementing caching. (NOTE: ![lighthouse](https://developer.chrome.com/blog/lighthouse-load-performance) might be useful for this step)