lastupdated init (tbc) + repo name change

Author: alistairwheeler

docs/documentation/integration/webservices/custom-services.md

@@ -3,11 +3,9 @@ sidebar_position: 60
 title: Custom services
 ---
 
-Custom services
-===============
+# Custom services
 
-Introduction
-------------
+## Introduction
 
 This document describes how to implement custom services (e.g. custom REST APIs) using external objects.
 
@@ -29,34 +27,35 @@ The calls examples are given using the `curl` command line tool
 > In versions 4.0+ a technical session is used to avoid taking care of the session cookie.
 
 For an application deployed on `myapp` webapp root, the base URL of the custom services is:
+
 ```
 http[s]://<host[:<port>]>/myapp/api/ext
 ```
-For an application deployed on the default webapp root, the base URL of the custom services is:  
+
+For an application deployed on the default webapp root, the base URL of the custom services is :
+
 ```
 http[s]://<host[:<port>]>/api/ext
 ```
+
 It will be noted `<base URL>` in the rest of the document.
 
 > **Warning**: In production the services endpoint's URL should be restricted only to allowed origins e.g. using URL filtering based on request's origin IP address or similar approaches.
 
-Scalability and performances
-----------------------------
+## Scalability and performances
 
 For optimal performances under high concurrent volume it may be useful to enable the API pooling by setting the `USE_WEBSERVICES_OBJECTPOOL` to `yes`, especially
 when using a single user (e.g. calls from a "public" frontend).
 
 This allow calls to the services to be processed by a per-user pool of external objects.
-The pool size can be adjusted/limied using the `WEBSERVICES_EXTOBJECTPOOL_MAXPEROBJECT`  and `WEBSERVICES_EXTOBJECTPOOL_MAXTOTAL` system parameters.
+The pool size can be adjusted/limied using the `WEBSERVICES_EXTOBJECTPOOL_MAXPEROBJECT` and `WEBSERVICES_EXTOBJECTPOOL_MAXTOTAL` system parameters.
 
-Service implementation
-----------------------
+## Service implementation
 
 A custom service is just a plain external object (check [this document](/docs/documentation/core/externalobject-code-examples) for general principles of external objects).
 
 In particular this external object needs to be granted to the user that will be calling it on the API endpoint.
 
-
 ### Java
 
 In **Java** as of version 4.0.P23 you can extends the more convenient `com.simplicite.webapp.services.RESTServiceExternalObject` helper class
@@ -91,34 +90,34 @@ public class MyServiceV1 extends com.simplicite.webapp.services.RESTServiceExter
 
 > **Note**: by default the non implemented method `get/post/put/del/head` of this helper class return a plain 400 ("Bad request") error.
 
-Service call
-------------
+## Service call
 
 Then the service could be called (using `POST` method in this example) like this:
+
 ```shell
-	curl <credentials> -X POST -H "Content-type:application/json" -d @req.json "<base URL>/MyServiceV1"
+curl <credentials> -X POST -H "Content-type:application/json" -d @req.json "<base URL>/MyServiceV1"
 ```
+
 Where, for instance if `req.json` is:
 
 ```json
 {
-	"name": "Bob"
+  "name": "Bob"
 }
 ```
 
 The result is then:
 
 ```json
 {
-	"request" : {
-		"name": "Bob"
-	},
-	"response": "Hello Bob!"
+  "request": {
+    "name": "Bob"
+  },
+  "response": "Hello Bob!"
 }
 ```
 
-Mapped business object services helper class
---------------------------------------------
+## Mapped business object services helper class
 
 As of version 4.0.P23 a high-level helper class `com.simplicite.webapp.services.RESTMappedObjectsExternalObject`
 is provided to simply expose Simplicit&eacute; business object CRUD in a simplified and customized way.
@@ -159,4 +158,3 @@ With the above mapping the user and responsibilities standard objects are availa
 - `/api/v1/users/1/user-resps` select (GET) the responsibilities of user with row ID `1`
 
 An OpenAPI schema is available on `/api/v1/openapi.yml`
-

docs/documentation/integration/webservices/git-repositories.md

@@ -3,17 +3,15 @@ sidebar_position: 20
 title: Git repositories
 ---
 
-Git repositories (/git)
-================
+# Git repositories (/git)
 
 As of **version 3.2 MAINTENANCE 03**, a new endpoint is available to export/import modules using [Git](https://git-scm.com/) over HTTP(S).
 
 This feature relies on the Eclipse [JGit](https://github.com/eclipse-jgit/jgit) library.
 
 > **Warning**: In production this Git endpoint's URL should be restricted only to allowed origins e.g. using URL filtering on request's origin IP address or similar approaches.
 
-Configuration
--------------
+## Configuration
 
 The Git repositories are stored on the server file system.
 
@@ -26,27 +24,26 @@ This can be done either:
 
 Then you also need to set the `USE_GIT` system parameter to `yes`.
 
-Export
-------
+## Export
 
 To export the `MyModule` module as a Git repository the first thing to do is to create or update the module's repository
 using the dedicated action on the _Module_ object:
 
 ![Commit module to Git repository](img/git-repositories/git-repositories-commitmodule.png)
 
 Then you can clone the module's repository by:
+
 ```shell
-	git clone http(s)://<host name>[/<app context root>]/git/<module name>
+git clone http(s)://<host name>[/<app context root>]/git/<module name>
 ```
+
 The credentials you have to use in this case are the same as the one you can use for the I/O interface.
 
-Import
-------
+## Import
 
 Any `git push [origin]` on the cloned module's repository triggers a module import (e.g. after having made some local changes or to upgrade another instance by pushing on another remote).
 
-Import from an origin remote
-----------------------------
+## Import from an origin remote
 
 It is possible to configure a module that is linked to an external Git repository by adding following settings to your module:
 
@@ -66,7 +63,7 @@ E.g. from another instance's module repository:
 Any call to the _Import module_ action will then result in either a clone or a pull on the configured remote Git repository.
 
 > Typical use case is to link a "secondary" instance to a "primary" instance. In such a case there are 2 possible ways to export/import a module from the "primary" to the "secondary" instance:
-> 
+>
 > - Directly use the _Import module_ action from the "secondary" instance (that will be pulling last commit(s) from the "primary" instance)
 > - Use a clone of the "primary" instance Git repository configured with an additional remote that points to the "secondary" instance.
 >   Then `git pull` will pull from the "primary" instance and `git push <remote name>` will push to the "secondary" instance.
@@ -87,8 +84,7 @@ E.g. from a **public** GitHub repository:
 As of version 5.2, you can set the JVM properties (`remote.git.username/password`) or the environment variables (`REMOTE_GIT_USERNAME/PASSWORD`)
 if you want to avoid configuring username/password credentials in your module's settings. A **much better approach** being to use a SSH URI with configured SSH public/private keys.
 
-Advanced
---------
+## Advanced
 
 The Git repositories created/cloned by Simplicit&eacute;:
 

docs/versions/release-notes/v5-1.md

@@ -1,6 +1,8 @@
 ---
 sidebar_position: 70
 title: ❌ v5.1
+last_update:
+  date: 2023-10-31
 ---
 
 Version 5.1.x release note

docs/versions/release-notes/v6-0.md

@@ -1,6 +1,8 @@
 ---
 sidebar_position: 40
 title: ❌ v6.0
+last_update:
+  date: 2024-10-31
 ---
 
 Version 6.0 release note

docusaurus.config.js

@@ -14,7 +14,7 @@ const config = {
   baseUrl: "/",
   // GitHub pages deployment config.
   organizationName: "simplicitesoftware", // Usually your GitHub org/user name.
-  projectName: "docusaurus", // Usually your repo name.
+  projectName: "documentation", // Usually your repo name.
   onBrokenLinks: "throw",
   onBrokenMarkdownLinks: "throw",
   onBrokenAnchors: "throw",
@@ -37,7 +37,7 @@ const config = {
       ({
         docs: {
           sidebarPath: "./sidebars.js",
-          showLastUpdateTime: true,
+          showLastUpdateTime: true
         },
         theme: {
           customCss: "./src/css/custom.css",
@@ -93,7 +93,7 @@ const config = {
       prism: {
         theme: prismThemes.github,
         darkTheme: prismThemes.dracula,
-        additionalLanguages: ['java'],
+        additionalLanguages: ['java', 'bash'],
       },
       algolia: {
         // The application ID provided by Algolia

package-lock.json

@@ -25,6 +25,7 @@
     "@mdx-js/react": "^3.0.0",
     "clsx": "^2.0.0",
     "prism-react-renderer": "^2.3.0",
+    "prismjs": "^1.30.0",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"
   },