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

App Request: Chibisafe #371

Open
5 of 7 tasks
cherryroots opened this issue Jun 19, 2024 · 7 comments
Open
5 of 7 tasks

App Request: Chibisafe #371

cherryroots opened this issue Jun 19, 2024 · 7 comments
Labels
AppRequest Request for new application

Comments

@cherryroots
Copy link

cherryroots commented Jun 19, 2024

Chibisafe

What does it do? Why? Please describe.

I'd like to have this included as the other services included in the sandbox either are too heavy(nextcloud) or not maintained anymore (Jirafeau). The following is the opening quote of the github page

Chibisafe is a file uploader service written in typescript that just works. It's easy to use, easy to deploy, free and open source. It accepts files, photos, documents, anything you imagine and gives you back a shareable link for you to send to others.

You can run it in public mode, user accounts mode or invite-only mode. Big files are automatically chunked to minimize network failure and users can create an API key to use the service programatically and hook it to other things.

The service also comes with a dashboard where you can edit almost every configuration of the instance directly from the UI without having to touch environment or configuration files manually. Control the name, the rate limit, max file size, accepted extensions, meta descriptions, etc directly from our intuitive panel.

Links to further information

What are you willing to do to help?

  • I will you help with making docs if this gets picked up.
  • I will you help with testing.
  • Other things:
@cherryroots cherryroots added the AppRequest Request for new application label Jun 19, 2024
@owine
Copy link
Collaborator

owine commented Jun 19, 2024

So this needs two underlying containers, Caddy serving the webui and then Saltbox's Traefik would be on top of that?

@saltydk
Copy link
Member

saltydk commented Jun 19, 2024

You don't need caddy, just multiple routers on the Traefik side to handle the 2 unique paths.

@owine
Copy link
Collaborator

owine commented Jun 19, 2024

You don't need caddy, just multiple routers on the Traefik side to handle the 2 unique paths.

Strange that their sample Traefik deployment still deploys Caddy in between.

@saltydk
Copy link
Member

saltydk commented Jun 19, 2024

Because they don't know what they are doing I suppose.

@saltydk
Copy link
Member

saltydk commented Jun 19, 2024

I mean they have this bit in their NPM guide:

As Docker by default does not run as your user, this may not be the best location to put Chibisafe in. The more "appropriate" location would be on /srv, so change the place where Chibisafe is installed accordingly if you want to follow best practices.

@saltydk
Copy link
Member

saltydk commented Jun 19, 2024

The only time I've needed another proxy as a go between is when using WSGI. There are probably other edge cases but it is the only one I could think of.

@cherryroots
Copy link
Author

cherryroots commented Jun 20, 2024

Yeah I don't think Caddy is required at all as the NPM guide doesn't use it, just a bit odd to have it with Traefik but I guess they don't know how to set up routers. The guide with NPM is only a week old too so guess nobody cared about not using Caddy before then

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

No branches or pull requests

3 participants