Customizable frontend #303

New Issue

michael · 2026-01-19T18:29:48Z

michael commented

2026-01-19 18:29:48 +00:00

Originally created by @telatin on GitHub.

I understand that the main website https://transfer.sh will be closing soon, unfortunately.
I tried the Docker container on a VM and it works very well, but it's odd that the homepage is branded "transfer.sh", and gives static examples of commands assuming that domain.

I think the source files for the front end should be provided to update them.

Thanks

Originally created by @telatin on GitHub. I understand that the main website https://transfer.sh will be closing soon, unfortunately. I tried the Docker container on a VM and it works very well, but it's odd that the homepage is branded "transfer.sh", and gives static examples of commands assuming that domain. I think the source files for the front end should be provided to update them. Thanks

michael closed this issue

2026-01-19 18:29:48 +00:00

michael commented

2026-01-19 18:29:49 +00:00

@mckaygerhard commented on GitHub:

https://github.com/dutchcoders/transfer.sh-web i think!

@mckaygerhard commented on GitHub: https://github.com/dutchcoders/transfer.sh-web i think!

michael commented

2026-01-19 18:29:49 +00:00

@paolafrancesca commented on GitHub:

as @mckaygerhard pointed out https://github.com/dutchcoders/transfer.sh-web is available: you can clone do the changes you want, and then use the new content with --web-path

@paolafrancesca commented on GitHub: as @mckaygerhard pointed out https://github.com/dutchcoders/transfer.sh-web is available: you can clone do the changes you want, and then use the new content with `--web-path`

michael commented

2026-01-19 18:29:49 +00:00

@mckaygerhard commented on GitHub:

umm the source files are not in the main repository?

@mckaygerhard commented on GitHub: umm the source files are not in the main repository?

michael commented

2026-01-19 18:29:49 +00:00

@telatin commented on GitHub:

Thanks! I will try that parameter.

_{Sent with GitHawk}

@telatin commented on GitHub: Thanks! I will try that parameter. <sub>Sent with <a href="http://githawk.com">GitHawk</a></sub>

michael commented

2026-01-19 18:29:49 +00:00

@paolafrancesca commented on GitHub:

@telatin you can already pass the --web-path option to transfer.sh in order to server static template pages. anyway I understand there's no documentation on what you have to pass to the templates (see https://github.com/dutchcoders/transfer.sh/blob/master/server/handlers.go#L164-L171 for a list)
I was already planning to change all references to transfer.sh in the frontend with the url of the actual domain the service is hosted on.

@paolafrancesca commented on GitHub: @telatin you can already pass the `--web-path` option to transfer.sh in order to server static template pages. anyway I understand there's no documentation on what you have to pass to the templates (see https://github.com/dutchcoders/transfer.sh/blob/master/server/handlers.go#L164-L171 for a list) I was already planning to change all references to `transfer.sh` in the frontend with the url of the actual domain the service is hosted on.

michael commented

2026-01-19 18:29:49 +00:00

@paolafrancesca commented on GitHub:

@bandicootdancing I see there are already instructions on transfer.sh-web readme how to setup what I've just explained:

docker run -d -v /folder:/uploads -v /folder/dist:/webapp --publish 5000:8080 dutchcoders/transfer.sh:latest --provider local --basedir /uploads --web-path /webapp/

obviously /folder and /folder/dist are just example: you can put whatever path you need for your setup and they don't even need to be nested like in the example

@paolafrancesca commented on GitHub: @bandicootdancing I see there are already instructions on transfer.sh-web readme how to setup what I've just explained: ``` docker run -d -v /folder:/uploads -v /folder/dist:/webapp --publish 5000:8080 dutchcoders/transfer.sh:latest --provider local --basedir /uploads --web-path /webapp/ ``` obviously `/folder` and `/folder/dist` are just example: you can put whatever path you need for your setup and they don't even need to be nested like in the example

michael commented

2026-01-19 18:29:49 +00:00

@paolafrancesca commented on GitHub:

@bandicootdancing transfer.sh-web is a go dependency of transfer.sh. In the first repository there should be full instruction on how to build the frontend with grunt and generate the go bindata depdency. After that you only need to copy the transfer.sh-web directory in the proper vendor position of transfer.sh, if you didn't already worked from there.

If you want to use the --web-path option on a transfer.sh docker container you just need to mount the content of the grunt generated frontend on the container. This mount can come or not from another container, but it is static content and I wouldn't see the reason for putting it in a container. Be aware that you only need the dist directory (target of the grunt build) of transfer.sh-web to be mounted, that's the reason why transfer.sh-web has no Dockerfile

@paolafrancesca commented on GitHub: @bandicootdancing transfer.sh-web is a go dependency of transfer.sh. In the first repository there should be full instruction on how to build the frontend with grunt and generate the go bindata depdency. After that you only need to copy the transfer.sh-web directory in the proper vendor position of transfer.sh, if you didn't already worked from there. If you want to use the `--web-path` option on a transfer.sh docker container you just need to mount the content of the grunt generated frontend on the container. This mount can come or not from another container, but it is static content and I wouldn't see the reason for putting it in a container. Be aware that you only need the `dist` directory (target of the grunt build) of transfer.sh-web to be mounted, that's the reason why transfer.sh-web has no Dockerfile

michael commented

2026-01-19 18:29:49 +00:00

@bandicootdancing commented on GitHub:

Options with some instructions would be appreciated. I don't see any normal instructions on setting this up without docker. I'm very new to docker so I'm almost lost at the moment with combining the two containers. Can someone write up some instructions on how to customize the transfer.sh-web along with this transfer.sh container? Do they both need to be used together?

I've seen other projects have a build process for the docker container. It'd be awesome to edit the frontend as needed then build if possible.

@bandicootdancing commented on GitHub: Options with some instructions would be appreciated. I don't see any normal instructions on setting this up without docker. I'm very new to docker so I'm almost lost at the moment with combining the two containers. Can someone write up some instructions on how to customize the transfer.sh-web along with this transfer.sh container? Do they both need to be used together? I've seen other projects have a build process for the docker container. It'd be awesome to edit the frontend as needed then build if possible.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#303