bump more progress

lincbrain · Apr 18, 2024 · a485fab · a485fab
1 parent 3bc3fcc
commit a485fab
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 13 deletions.
diff --git a/docs/60_initialize_vendors.md b/docs/60_initialize_vendors.md
@@ -376,8 +376,7 @@ alt="retrieve"
 style="width: 60%; height: auto; display: block; margin-left: auto;  margin-right: auto;"/>
 <br/><br/>
 
-Your frontend should be able to deploy to an auto-generated URL via Netlify now! Steps for domain management and configuration are described further in the [Frontend Deployment](.
-./42_frontend_deployment) section of these docs.
+Your frontend should be able to deploy to an auto-generated URL via Netlify now! Steps for domain management and configuration are described further in the [Frontend Deployment](../64_dandi_archive/#frontend-deployment) section of these within the DANDI Archive setup.
 
 ## Sentry
 

diff --git a/docs/61_dandi_authentication.md b/docs/61_dandi_authentication.md
@@ -52,9 +52,11 @@ After creating this object, you are all set in the Django Admin panel for now.
 
 ## Populating appropriate values for the frontend to handle authentication
 
+This step assumes that you have successfully set up your Netlify account:
 
 
-## Configuring Migrations for Initial Auth Setup
+
+## Referencing Authentication credentials from migrations in DANDI Archive
 
 
 
diff --git a/docs/64_dandi_archive.md b/docs/64_dandi_archive.md
@@ -1,8 +1,6 @@
 # Work In Progress
 
-This step assumes that you have completed all steps in: 
-• [Initialize Vendors](../60_initialize_vendors)
-• [DANDI Infrastructure](../63_dandi_infrastructure)
+This step assumes that you have completed all steps in: [Initialize Vendors](../60_initialize_vendors) & [DANDI Infrastructure](../63_dandi_infrastructure)
 
 ## Initial Steps
 
@@ -22,11 +20,11 @@ Which process, the resources allocated to that process, and how that process is
 DANDI Archive defines a [Procfile](https://github.com/dandi/dandi-archive/blob/master/Procfile). In this `Procfile`,
 you'll see several entries:
 
-• `release`: a command that is run each time a new version of DANDI API is pushed to Heroku
-• `web`: runs `gunicorn`, a persistent server that handles HTTP requests for the DANDI API
-• `worker`: a worker process that runs `celery` behind-the-scenes. `celery` handles tasks that would otherwise cause the API to timeout
-• `checksum-worker`: another worker, also using `celery`, that specifically calculates if a new file pushed to DANDI Archive is new/updated, and determines what exactly has been changed
-• `analytics-worker`: another `celery` worker that handles all tasks related to processing of S3-related logs
+- `release`: a command that is run each time a new version of DANDI API is pushed to Heroku.
+- `web`: runs `gunicorn`, a persistent server that handles HTTP requests for the DANDI API.
+- `worker`: a worker process that runs `celery` behind-the-scenes. `celery` handles tasks that would otherwise cause the API to timeout.
+- `checksum-worker`: another worker, also using `celery`, that specifically calculates if a new file pushed to DANDI Archive is new/updated, and determines what exactly has been changed.
+- `analytics-worker`: another `celery` worker that handles all tasks related to processing of S3-related logs.
 
 This `Procfile` shouldn't need to be changed or reconfigured much for a DANDI-clone; however, it is important to note so that one may understand how DANDI Archive is working.
 
@@ -96,8 +94,8 @@ You are all set here!
 
 ## Updating Allowed Hosts
 
-## Referencing Authentication credentials from migrations
-
 ## Approval of Users
 
+## Frontend Deployment
+
 ## Setting up Staging Environments