mirror of
https://github.com/dutchcoders/transfer.sh.git
synced 2026-02-03 14:13:26 +00:00
The readme file doesn't explain how to deploy a server for a VPS #81
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @W01v3n on GitHub.
I really don't get it, why always make the right documentation for docker and not for a VPS? I am using a VPS and I don't want to use docker, why are you forcing me? How can I deploy it like an oldschooler with nginx?? Please!
@W01v3n commented on GitHub:
@aspacca Well, I got a VPS with NGINX on it that's using port 443. And I'd like to keep using NGINX with port 443 but I also want to include a virtual host for transfer.sh, even through a reverse proxy. How can I do that? I didn't see anything on the docs that can help with that.
Thanks!
@paolafrancesca commented on GitHub:
@W01v3n do you already know how to set up a virtual host on nginx, using it as a reverse proxy to a backend service?
@W01v3n commented on GitHub:
@aspacca I do know how to set up a virtual host on NGINX, but I have less experience doing it as a reverse proxy.
That's why I can really use a guide for that, because I really want to use transfer.sh, but I want to have control on how I serve it via NGINX.
@paolafrancesca commented on GitHub:
there's nothing different for using nginx as reverse proxy for transfer.sh than for anything else
here's a template
you then start transfer.sh with tls listener, using the same files as the one defined in the nginx configuration
I will add this to the readme as soon as I will have time
@paolafrancesca commented on GitHub:
@W01v3n what are the information you are missing in order to deploy?
@W01v3n commented on GitHub:
I'll definitely try that, thanks a lot @aspacca !!!
@W01v3n commented on GitHub:
@aspacca That can work, great.
Now I just need to know how can I make it work with the web interface as well.
Maybe you can help even further with explaining that too, or am I being a little too greedy?
Thanks a lot!
@W01v3n commented on GitHub:
@aspacca
Oh, I thought that it wouldn't work because there is a different repository for the web interface:
https://github.com/dutchcoders/transfer.sh-web
@paolafrancesca commented on GitHub:
do you have a dns entry for
%YOUR.DOMAIN%pointing to%YOUR.IP%?that's it
if
curl --upload-file etcis working then you can just open https://%YOUR.DOMAIN%@W01v3n commented on GitHub:
@aspacca The original repository does not include any HTML files..
I went to this repository https://github.com/dutchcoders/transfer.sh-web
and I did everything that was instructed, but it's still not complete, the dist directory was created but nothing inside it but fonts.
@paolafrancesca commented on GitHub:
because the files are embegged in a go file in the transfer.sh-web package that's used as depdency
unless you want to customise the frontend there's no need for html files
@paolafrancesca commented on GitHub:
I have the impression you need much more documentation than just the one about running/seting up transfer.sh
Given your behaviour against the code of conduct, and not being me interested in adding a 101 about go in the documenation I'm going to close this issue
@W01v3n commented on GitHub:
Look, I'm pretty 100% sure that nobody got this to work. It looks like this entire is project is corrupt and broken to begin with, so before you will completely tarnish the name of go, I'm going to stop trying. Just so you know, running the command
go run main.go --web-path /home/transfersh/transfer.sh-web/src --basedir /home/transfersh/basedirgives the following hideous output:
I've given up, I don't think anyone got this thing to work.
You really should work on your documentations and your code, 'cause it doesn't work at all.