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 #221

Open
hajika opened this issue May 25, 2017 · 1 comment
Open

Image upload #221

hajika opened this issue May 25, 2017 · 1 comment

Comments

@hajika
Copy link
Contributor

hajika commented May 25, 2017

I see, that there is no wish to build a cms like upload system in jingo (like you pointed out here #176) but I think that images are very essential for wiki documentations. Currently I have the problem, that I don't know exactly what the best way is to serve my users possibilities to add files to the wiki. I dont want them, to upload the files anywhere in the web. So I created a public folder to our Nextcloud where they can upload the images and then add it to the wiki.

That might work, but its still painful to log in to nextcloud first and then put the images there, get the link, put the link to the wiki. And also the wiki image folder must be public, even when its hidden behind a random url it would be much better to have a function within the wiki secured by the wiki login.

I agree that a file upload system would bloat the software, but simple image add and remove function seems to me essential for a wiki.

@claudioc
Copy link
Owner

Some days ago I wrote a wiki post here about the image embedding feature https://github.com/claudioc/jingo/wiki/add-images-to-the-Jingo-own-repository

Nothing probably anywhere near the "solution" to your problem, but some more food for thoughts :)

I know that "Media upload" is one of the most requested feature for Jingo and I am definitely considering an implementation which would not bloat everything up...

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

No branches or pull requests

2 participants