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 Save Location #316

Closed
ArcaneTSGK opened this issue May 14, 2019 · 4 comments
Closed

Image Save Location #316

ArcaneTSGK opened this issue May 14, 2019 · 4 comments
Milestone

Comments

@ArcaneTSGK
Copy link

We currently have an instance of our CMS deployed to AWS EC2 via CodeDeploy, during this process the application is removed from the server with the latest version of the application being deployed.

This of course removes everything under App_Data, meaning all image files on the server are lost on every deployment.

Is there a way to configure the image upload in CoFoundry to save the images to another location, ideally this would be a separate drive on the server, or at the very least a directory outside of the application?

@HeyJoel HeyJoel added this to the 0.8 milestone May 14, 2019
@HeyJoel
Copy link
Member

HeyJoel commented May 14, 2019

There's two ways you could resolve this, one is to change the Cofoundry:FileSystemFileStorage:FileRoot setting e.g.

appsettings.json

{
  "Cofoundry": {
    "FileSystemFileStorage:FileRoot": "F:\\Files\\MySite",
  }
}

The other method would be to use a plugin like Cofoundry.Plugins.Azure if you were using Azure, which would allow you to use blob storage. Unfortunately there's no S3 equivalent plugin at the moment, but I think it would be fairly easy to create one if you wanted to go down that route, all you'd need to do is create an IFileStoreService implementation and register it to override the base implementation

We should add some documentation on this either in the deployment docs or the assets docs

@ArcaneTSGK
Copy link
Author

Thank you for your quick response, would you like me to leave this issue open for now as a reminder to add documentation?

Cheers!

@HeyJoel
Copy link
Member

HeyJoel commented May 14, 2019

Yes please, I think we need to update the docs.

@HeyJoel HeyJoel modified the milestones: 0.13, 0.12 Mar 27, 2024
@HeyJoel
Copy link
Member

HeyJoel commented Apr 4, 2024

Documentation complete, will be published with the v0.12 release.

@HeyJoel HeyJoel closed this as completed Apr 4, 2024
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

2 participants