diff --git a/2024/01/14/papermerge-301-release/index.html b/2024/01/14/papermerge-301-release/index.html index 422fc69..400e601 100644 --- a/2024/01/14/papermerge-301-release/index.html +++ b/2024/01/14/papermerge-301-release/index.html @@ -464,8 +464,7 @@ in - announcement, - papermerge3 + announcement diff --git a/archive/2024/index.html b/archive/2024/index.html index 6f10110..279aa7d 100644 --- a/archive/2024/index.html +++ b/archive/2024/index.html @@ -452,8 +452,7 @@

2024

  • in - announcement, - papermerge3
    • + announcement diff --git a/category/announcement/index.html b/category/announcement/index.html index 2b1098e..4e689fe 100644 --- a/category/announcement/index.html +++ b/category/announcement/index.html @@ -452,8 +452,7 @@

    announcement

  • in - announcement, - papermerge3
    • + announcement diff --git a/category/papermerge3/index.html b/category/papermerge3/index.html index 9ff9338..dab40b5 100644 --- a/category/papermerge3/index.html +++ b/category/papermerge3/index.html @@ -444,56 +444,6 @@

    papermerge3

    -
    - - -
    -
    -
    -

    Papermerge 3.0.1 Release

    -

    I am happy to announce the release of version 3.0.1.

    -

    Among other things, this release fixes major issue related to -DB connections. -Let me provide short description of the problem. -The access to specific REST API endpoints was leaving DB connection open. The -problem is that open DB connection were accumulating up to the point -(which depends on specific DB configuration) when DB was refusing to accept -more DB connections, which resulted of course to the whole app going -offline.

    -

    The root course of the problem is Django ORM and the way it handles DB -connections. To mitigate the issue, we've decided start moving away from -Django ORM to SQLAlchemy. Of course full transition to new ORM will span many -releases, but the main point here is that for end users this transition is -fully opaque.

    - -
    -
    - -
    -
    -
    • diff --git a/index.html b/index.html index 1da0f5d..74a1d86 100644 --- a/index.html +++ b/index.html @@ -448,8 +448,7 @@

      Blog

    • in - announcement, - papermerge3
      • + announcement diff --git a/search/search_index.json b/search/search_index.json index 68acd7b..8243edb 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -1 +1 @@ -{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Blog","text":""},{"location":"2023/12/29/papermerge-30/","title":"Papermerge 3.0","text":"

      I am very excited to announce the release of Papermerge DMS 3.0.

      Comparatively to all previous releases, version 3.0 underwent serious architectural changes. I won't bore reader with all technical details, I will just briefly mention two biggest technical changes:

      • frontend rewritten in TS/React
      • REST API now served with FastAPI

      Also, the format of storing files on the disk differs from previous versions - alone this fact makes version 3.0 incompatible with all previous releases.

      Here is the list of exciting features that version 3.0 brings:

      • support for jpeg/png/tiff formats is back
      • full text search is now backed up by Solr search engine
      • multiple authentication backends are supported e.g. oauth2.0/OIDC (not documented yet)
      • well documented REST API
      • dual panel mode
      • page management - delete, reorder, rotate, merge, move pages between documents
      • OCR with text overlay (thanks to OCRMyPDF)

      Go to 3.0 documentation and play with docker compose setup. Also, for production deployment on remote server there Ansible playbook available as well.

      Enjoy!

      ","tags":["papermerge3","announcement",3.0]},{"location":"2024/01/14/papermerge-301-release/","title":"Papermerge 3.0.1 Release","text":"

      I am happy to announce the release of version 3.0.1.

      Among other things, this release fixes major issue related to DB connections. Let me provide short description of the problem. The access to specific REST API endpoints was leaving DB connection open. The problem is that open DB connection were accumulating up to the point (which depends on specific DB configuration) when DB was refusing to accept more DB connections, which resulted of course to the whole app going offline.

      The root course of the problem is Django ORM and the way it handles DB connections. To mitigate the issue, we've decided start moving away from Django ORM to SQLAlchemy. Of course full transition to new ORM will span many releases, but the main point here is that for end users this transition is fully opaque.

      ","tags":["papermerge3","announcement",3.0]},{"location":"archive/2024/","title":"2024","text":""},{"location":"archive/2023/","title":"2023","text":""},{"location":"category/announcement/","title":"announcement","text":""},{"location":"category/papermerge3/","title":"papermerge3","text":""}]} \ No newline at end of file +{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Blog","text":""},{"location":"2023/12/29/papermerge-30/","title":"Papermerge 3.0","text":"

      I am very excited to announce the release of Papermerge DMS 3.0.

      Comparatively to all previous releases, version 3.0 underwent serious architectural changes. I won't bore reader with all technical details, I will just briefly mention two biggest technical changes:

      • frontend rewritten in TS/React
      • REST API now served with FastAPI

      Also, the format of storing files on the disk differs from previous versions - alone this fact makes version 3.0 incompatible with all previous releases.

      Here is the list of exciting features that version 3.0 brings:

      • support for jpeg/png/tiff formats is back
      • full text search is now backed up by Solr search engine
      • multiple authentication backends are supported e.g. oauth2.0/OIDC (not documented yet)
      • well documented REST API
      • dual panel mode
      • page management - delete, reorder, rotate, merge, move pages between documents
      • OCR with text overlay (thanks to OCRMyPDF)

      Go to 3.0 documentation and play with docker compose setup. Also, for production deployment on remote server there Ansible playbook available as well.

      Enjoy!

      ","tags":["papermerge3","announcement",3.0]},{"location":"2024/01/14/papermerge-301-release/","title":"Papermerge 3.0.1 Release","text":"

      I am happy to announce the release of version 3.0.1.

      Among other things, this release fixes major issue related to DB connections. Let me provide short description of the problem. The access to specific REST API endpoints was leaving DB connection open. The problem is that open DB connection were accumulating up to the point (which depends on specific DB configuration) when DB was refusing to accept more DB connections, which resulted of course to the whole app going offline.

      The root course of the problem is Django ORM and the way it handles DB connections. To mitigate the issue, we've decided start moving away from Django ORM to SQLAlchemy. Of course full transition to new ORM will span many releases, but the main point here is that for end users this transition is fully opaque.

      ","tags":["announcement"]},{"location":"archive/2024/","title":"2024","text":""},{"location":"archive/2023/","title":"2023","text":""},{"location":"category/announcement/","title":"announcement","text":""},{"location":"category/papermerge3/","title":"papermerge3","text":""}]} \ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index 6631d14..be3c094 100644 Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ