Share files securely over the internet for a day.
See more information about TempFiles here.
The following text describes how to install the static website (Frontend).
For instructions on how to install the Backend service responsible for the encryption and storage of uploaded files, see tempfiles-download/Backend.
TempFiles Frontend is primarily built to be hosted on CDNs as a static website.
It's therefore trivial to use GitHub Pages to host the website for free:
- Fork this repository.
- Edit the URLs in _config.yml to reflect your Backend server's address.
- Select
master
as source branch and/ (root)
as source path on Settings > Pages - (Optionally) Create a
CNAME
file with your desired domain name and point your domain to<username>.github.io
.
To run the frontend site for your own TempFiles instance using Docker, do the following:
- Download
docker-composer.json
and_config.yml
. - Edit the URLs in _config.yml to reflect your backend server's address.
- (Optionally) change the repository value in _config.yml.
- (Optionally) Open docker-compose.yml and forward port
4000
to your desired outgoing port. - Run
docker-compose up -d
. - The frontend should now be reachable on the outgoing port you selected in step 4. A reverse proxy is recommended for TLS.
Here's how to install and run the Frontend of TempFiles locally without Docker:
-
Download the code
git clone https://github.com/tempfiles-download/Frontend.git Frontend cd $_
-
Install Ruby
sudo snap install ruby --classic
-
Install the required Ruby gems 💎
bundle install --path vendor/bundle
-
Run minification and cleanup scripts
./_scripts/*.sh
-
Build the site
bundle exec jekyll build
-
Either:
-
Point your web server or reverse proxy server to the newly generated
_site/
directory. -
Set up a simple web server with:
bundle exec jekyll serve
```
- If you're going to use your own backend server, remember to change the URL values in
_config.yml
.
See something missing in TempFiles? Contributions are appreciated!
Before doing changes to the code of TempFiles make sure you write in a program that complies with our EditorConfig.
You can also create a new issue.