Merge pull request #361 from hydroserver2/v1.7.0

V1.7.0

Author: kjlippold

README.md

@@ -31,8 +31,7 @@ HydroServer consists of the following components:
 - Cross platform app for running on Windows, Mac, or Linux
 - Silent updater for loading data to a HydroServer instance from delimited text files
 - Python package (used by the app) for loading data to HydroServer via the SensorThings API
-- Streaming Data Loader Desktop app repository: [https://github.com/hydroserver2/hydroloader-desktop](https://github.com/hydroserver2/hydroloader-desktop)
-- HydroLoader Python package repository: [https://github.com/hydroserver2/hydroloader](https://github.com/hydroserver2/hydroloader)
+- Streaming Data Loader Desktop app repository: [https://github.com/hydroserver2/streaming-data-loader](https://github.com/hydroserver2/streaming-data-loader)
 
 ## History
 

docs/.vitepress/config.ts

@@ -110,10 +110,10 @@ export default defineConfig({
                 text: "Customize the Data Management App",
                 link: "/how-to/data-management-app/customize.md",
               },
-              {
-                text: "Archive Data to HydroShare",
-                link: "/how-to/data-management-app/hydroshare-archive.md",
-              },
+              // {
+              //   text: "Archive Data to HydroShare",
+              //   link: "/how-to/data-management-app/hydroshare-archive.md",
+              // },
             ],
           },
           {

docs/how-to/deployment/production-deployment-overview.md

@@ -332,6 +332,37 @@ When deploying HydroServer in production, you should implement multiple layers o
   unauthorized access attempts, and to track overall system health. HydroServer also provides a `/health-check` 
   endpoint that can be used by external monitoring services.
 
+### Enabling Celery for HydroServer
+
+HydroServer optionally supports Celery for scheduling background tasks. To run Celery, you must set up several 
+additional services, including at least one worker instance, a scheduler, and a broker such as
+[Redis](https://redis.io/docs/latest/).
+
+The following HydroServer settings can be used to configure Celery:
+
+- **CELERY_ENABLED**  
+  Controls whether Celery scheduling is enabled. If not enabled, all data processing will be handled by HydroServer's
+  web server.
+  Example: `True` / `False`
+
+- **CELERY_BROKER_URL** 
+  The URL of the broker service Celery should use to orchestrate tasks.
+  Example: `redis://127.0.0.1:6379/0`
+
+To start a Celery worker, use the following entrypoint command with HydroServer’s Docker image. This container must
+have database and broker access.
+
+```bash
+celery -A hydroserver worker --loglevel=INFO
+```
+
+To start a Celery scheduler, use the following entrypoint command with HydroServer’s Docker image. This container must
+have database and broker access.
+
+```bash
+celery -A hydroserver beat --loglevel=INFO
+```
+
 ### HydroServer Management Commands
 
 After provisioning your infrastructure, but before starting HydroServer’s web server, you must run several management 
@@ -435,17 +466,6 @@ dashboard.
    - Sensors  
    - Units  
 
-6. **Configure HydroShare Archival** (optional / experimental)  
-   - First, configure HydroShare as a social application (see Step 4).  
-   - Update the social application record with the following JSON:  
-     ```json
-     {
-       "allowSignUp": false,
-       "allowConnection": true
-     }
-     ```  
-   - Navigate to **Orchestration Systems** > **Add Orchestration System**.  
-     - Create a new record with:  
-       - **Name**: `HydroShare Archival Manager`  
-       - **Type**: `HydroShare`  
-   - *Note: This archival configuration method is temporary and will be deprecated in a future release.*
+6. **Configure HydroServer ETL** (optional)
+   If you have set up a HydroServer Celery scheduler and worker, you 
+