Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image Upload Path flexibility for deployment and workflow #187

Open
stevewh opened this issue Oct 28, 2020 · 3 comments
Open

Image Upload Path flexibility for deployment and workflow #187

stevewh opened this issue Oct 28, 2020 · 3 comments

Comments

@stevewh
Copy link
Collaborator

stevewh commented Oct 28, 2020

There is a current configuration issue where processing systems have to match deployment systems in image file directory structures. Currently you can define the "document root" relative path for uploaded images and the URL is calculated and stored into the database. This is further problematic that the code doesn't allow grouping of the images as the current code creates a directory for each db using DBNAME and a subdir named using the "txt"+txt_id of the Text entity that makes it difficult to phase work or divide work using separate databases.

@stevewh
Copy link
Collaborator Author

stevewh commented Oct 28, 2020

The proposed solution is to adjust the path for uploaded files to default as it is currently and use some new configuration CONSTANTS in config.php to direct teh algorithm.
IMAGEPATHUSEINVNO a boolean which directs the image code to use the txt_ckn in place of the text tag 'txt'+txt_id for the subdir
IMAGEDBPATH which is an umbrella directory to aggregate images which default to DBNAME to aggregate by database. Note that an empty string will place images in subdirs according to the above under the IMAGE_ROOT

@stevewh stevewh added the Spec label Oct 28, 2020
@xadxura
Copy link
Collaborator

xadxura commented Oct 28, 2020

Issue description looks good to me. Thanks!

@IanMcCrabb
Copy link
Collaborator

Looks like we can take advantage of the new capability at some stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants