• Use mongodb-model driver: https://github.com/zakodium/adonis-mongodb#using-with-the-authentication-provider
• Login the user with ctx.auth.login(user) for all methods
• Add a field to the session that contains the login method that was used. Let's call it mylims.auth.method. (We'll use it for custom logout hooks and/or to indicate that information in the API)
• There should no longer be the need for our custom AuthManager

if the file between sync and import is removed or relocated it could error

• Define roles
• Define directives for authorization

In one of the steps, we need to update the "providers" list in .adonisrc.json (remove providers starting with ./addons/). This allows us to develop with all the addons locally.

• Design of organization
• Customization on visualization of pages based on organization (frontend)

• Relation between samples
• Relation with users
• Relation with organizations

I'm thinking we should decide on a metadata file that add-ons should implement.
Then, instead of having magical files loaded automatically (like routes.ts), the metadata would contain that information.
It would also contain user-friendly name and description for the addon, which can be used in the user interface.

in config/app.ts:

generateRequestId: true,

Where do we store logs?
Do we allow to read the logs from the application?
What are the rules about logging within the application?

that loads fs-synchronizer.

https://github.com/mylims/new-eln-server/blob/43db95e88d7cacc24775e91917e3801c3f6096d4/providers/user/UserModel.ts

• Local server with Docker
• Files in local drive
• Files in S3-like system
• Deploy in GCP
• Kubernetes?

This will allow to change the main settings of the application, like MongoDB connection, ... (things that are in the config directory)
Enable and disable addons.

this will avoid the loose of focus

• LDAP addon is enabled?
• getEnabledAddons()
• list of addons to check

I've been looking into why the session initiated from LDAP login doesn't work, and actually we're doing it wrong.
There should be only one guard for all possible user sources.

Maybe it can be done with docker image parameters.

It will be usefull to have some documentation on the process for files importation

• search flat with filters (status, creation date, update at), pagination
• sort by default is revisions.0.date
• github graphql inspiration for sortBy and filterby, pagination (skip, limit)
• add the modification date column

Just pasting this here. I haven't looked into it: https://plate.udecode.io/

why use a Makefile rather than npm scripts?

I also would not expect to reset everything and re-install dependencies everytime I start my development environment

Originally posted by @stropitek in #20 (comment)

we can do it like this temporarily but this won't work for binary files. we should aim for only returning a URL in the GraphQL API and serve the file separately (with an Adonis route)

Originally posted by @targos in #109 (comment)

• Organization defines what is the hierarchy of samples
• Possible restrictions of hierarchy of samples (form sample you only can have chip, not the contrary for example)

I got an error that NEXT_PUBLIC_API_URL is not defined but I don't know how to define it or what value to put.

will it fail?

https://github.com/mylims/mylims/blob/master/addons/file-sync/Commands/Sync.ts#L34
https://github.com/mylims/mylims/blob/master/addons/file-sync/Commands/Import.ts#L49
https://github.com/mylims/mylims/blob/master/addons/file-sync/Commands/Integrity.ts#L39

With unique constraint

Username and password hash stored in a MongoDB collection

• now everything is queried, the idea will be only query the specific level
• add depth to fileSync
• escape regular expression for the query
• escape-string-regexp

• track of latest topic addressed
• keep historical of status
• trigger of a push on event to a processor

Related: https://twitter.com/wesbos/status/1346627621329768448

When a someone logs in, a User is searched in the users DB using 3 parameters

• provider name (local or ldap for now)
• provider unique id (MongoDB _id for local, uid for ldap)
• email

1. Search with provider name + provider unique id
2. If found, return user
3. If not found, search with email
4. If found, update provider info and return user
5. If not found, create and return new user

this doesn't allow to go back easily to previous page

https://github.com/adonisjs/auth/releases/tag/v8.0.0

Todo:

• Use an enum to describe the status of a revision
• Fix error on panel admin (hostUrl undefined)
• Rename "files" collection with a prefix
• "Check" command that works on "files" collection with same options as "Sync" command
• Create a new collection that store imported files
• It may be possible to config the storage location on admin panel

Imported files naming strategy

When imported, files must be organized like this:

• Filename: random UUID
• Extension: original file extension
• Location: subfolderA/subfolderB/filename.extension
  With subfolderA defined as the two first characters of the UUID and subfolderB defined as the two next characters of the UUID.

Check command workflow

for each file related to the given file_sync_option with last revision set to "pending" state
    if ready checks are okay
        set state to "importing"
        copy the file on our system
        generate a new subfolder to store the imported file
        set state to "imported"
    else
        test next file

• Field definitions
• Samples CRUD

• Validate max is bigger than min
• validate that size is convertible to bytesize