Skip to content

Releases: atomicdata-dev/atomic-server

v0.26.1

06 Oct 20:04
Compare
Choose a tag to compare
  • Improved error message for hierarchy authorization check #178
  • Fix Property recommends #177
  • Refuse commits with query parameters in their subjects #179
  • Add resource.destroy() method, which uses commits
  • Improve killing existing processes - wait until other process has stopped #167
  • Make atomic-cli smaller (don't use db feature from atomic-lib)

v0.26.0

22 Sep 06:29
Compare
Choose a tag to compare
  • Added WebSockets support for live synchronization / real-time updates with the front-end #171
  • Update index after destroying a resource #173

v0.25.6

16 Aug 16:09
Compare
Choose a tag to compare
  • Fix domain .env #169
  • Fix HTTPS port bug

v0.25.5

16 Aug 15:43
Compare
Choose a tag to compare
  • Check and terminate running instances of atomic-server when running instance

v0.25.4

14 Aug 11:58
Compare
Choose a tag to compare
  • Add flags for reindex and init
  • Improve CI for automated tests & builds #165

v0.25.3

13 Aug 08:44
Compare
Choose a tag to compare
v0.25.3 Pre-release
Pre-release

v0.25.3

  • Improve ease of initial setup with initial invite on /setup #159 and welcoming descriptions for first Drive and Invite.

v0.25.2

  • Fixes caching bugs for collections introduced by #14
  • Fix external resources in Collections #161

v0.25.1

  • Add Value indexing, which speeds up TPF queries / collections tremendously #14
  • Add models for Document editor
  • Improve commit authorization checks - allow new resources with existing parents

v0.24.2

  • Fix /path endpoint return values #143
  • Add ASCI logo in terminal on boot
  • Fix getting resources from server's /commit path #144
  • Fix cache-control header issue when opening a closed tab #137
  • Add collection properties name, sortBy and sortDesc #145
  • Extract apply_changes from apply_commit, make versioning safer and more reliable #146
  • Remove AD3 remnants, clean up code #148
  • TPF endpoint supports JSON-AD #150
  • Custom serializations in atomic-cli tpf

v0.24.1

  • Add write rights to Agent itself on accepting Invite
  • Fix RDF serialization for dynamic resources #141
  • Update and check Usages for Invites #134
  • Make names for agents optional
  • Move shortname property always to first one

v0.24.0

09 Jun 07:28
Compare
Choose a tag to compare
v0.24.0 Pre-release
Pre-release

Lots of changes, related to the introduction of Hierarchy.

  • Hierarchy with breadcrumbs and easy to use navigation #132
  • Authorization using Hierarchy, which means you can add write & read permissions anywhere in a hierarchy.
  • Invites to invite new and existing users to read / edit a bunch of resources. Test it https://atomicdata.dev/invites/1 #134
  • Sidebar for easier navigation.
  • Fixes, all kinds of fixes.

v0.23.0

27 Mar 21:01
Compare
Choose a tag to compare
v0.23.0 Pre-release
Pre-release
  • Added versioning #42
  • Added endpoints #110 #73
  • Moved /path logic to atomic-lib as endpoint #110
  • get_extended_resource is now DB only #110
  • Correct response codes (404) #105
  • Improved .html page (+PWA support and Matomo tracking)
  • Upgraded various dependencies

v0.22, v0.21.x changes:

  • Reject commits if they are editing a non-owned resource #106
  • Correct response codes (404) #105
  • Use atomic-data-browser js frontent by default #103
  • Fix deleting items #101
  • Add a datatype for floats #93.
  • Switch to JSON-AD parsing & serialization for Commits #100
  • Change Commit serialization to match atomic-data-browser implementation #98.
  • Permissive CORS #92

v0.21.0

24 Jan 19:19
Compare
Choose a tag to compare
v0.21.0 Pre-release
Pre-release
  • Add JSON-AD serialization #79, use it in Commits
  • Servers are aware of their own URL #51
  • Improved CLI edit feature, more flexible (create new resources if none exist, fix newlines)
  • Add resource.save_locally()

v0.20.0

08 Jan 19:58
Compare
Choose a tag to compare
v0.20.0 Pre-release
Pre-release
  • Huge refactor of internals. Got rid of all string representations for Atoms, so store should only contain valid data. All Resources have all required props, and data is of the correct datatype.
  • Resource.save() can be called! Easy way to store changes, both locally and externally.
  • Added collection sorting #63