You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: turing-aem/aem-plugin-sample/README.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,12 +186,6 @@ The connector will:
186
186
3. Connect to Turing server
187
187
4. Start indexing content from the configured root path
188
188
189
-
### Monitoring
190
-
191
-
-**H2 Console**: Access at `http://localhost:8080/h2-console` (if enabled)
192
-
-**Logs**: Monitor console output for indexing progress
193
-
-**Turing Dashboard**: Check indexed content at your Turing URL
194
-
195
189
### Custom Extensions
196
190
197
191
To create your own extensions:
@@ -248,4 +242,4 @@ Enable debug logging by adding to your run command:
248
242
3.**Create custom extensions**: Implement your own content processors
249
243
4.**Test with real content**: Replace WKND with your actual AEM content structure
250
244
251
-
This sample provides a foundation for building production-ready AEM-to-Turing integrations. Customize the extensions and configuration to match your specific content models and indexing requirements.
245
+
This sample provides a foundation for building production-ready AEM-to-Turing integrations. Customize the extensions and configuration to match your specific content models and indexing requirements.
0 commit comments