Mirrors/send
1
0
Fork 0
mirror of https://gitlab.com/timvisee/send.git synced 2025-12-06 14:10:53 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove Firefox branding from app name in documentation and other files

Browse Source
This commit is contained in:
timvisee
2020-10-15 18:52:41 +02:00
parent e77d2b3722
commit 561ed3994e
9 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/acceptance-mobile.md
View File

@@ -7,7 +7,7 @@
Adapted from [this spreadsheet](https://airtable.com/shrkcBPOLkvNFOrpp)
- [ ] It should look and feel of an Android App
- [ ] It should look and feel like the Firefox Send Web Client
- [ ] It should look and feel like the Send Web Client
### Main Screen
- [ ] It should clearly Indicate the name of the product
@@ -59,7 +59,7 @@ Adapted from [this spreadsheet](https://airtable.com/shrkcBPOLkvNFOrpp)
- [ ] It should allow users to opt into notifications when their link is downloaded
## Annotations on Mobile Spec
This document tracks differences between the UX spec for Firefox Send and the intended MVP.
This document tracks differences between the UX spec for Send and the intended MVP.
[Spec Link](https://mozilla.invisionapp.com/share/GNN6KKOQ5XS)

10
docs/deployment.md
View File

@@ -1,5 +1,5 @@
## Requirements
This document describes how to do a full deployment of Firefox Send on your own Linux server. You will need:
This document describes how to do a full deployment of Send on your own Linux server. You will need:
* A working (and ideally somewhat recent) installation of NodeJS and NPM
* GIT
@@ -12,14 +12,14 @@ For Debian/Ubuntu systems this probably just means something like this:
## Building
* We assume an already configured virtual-host on your webserver with an existing empty htdocs folder
* First, remove that htdocs folder - we will replace it with Firefox Send's version now
* First, remove that htdocs folder - we will replace it with Send's version now
* git clone https://github.com/mozilla/send.git htdocs
* Make now sure you are NOT root but rather the user your webserver is serving files under (e.g. "su www-data" or whoever the owner of your htdocs folder is)
* npm install
* npm run build
## Running
To have a permanently running version of Firefox Send as a background process:
To have a permanently running version of Send as a background process:
* Create a file "run.sh" with:
```
@@ -29,11 +29,11 @@ nohup su www-data -c "npm run prod" 2>/dev/null &
* chmod +x run.sh
* ./run.sh
Now the Firefox Send backend should be running on port 1443. You can check with:
Now the Send backend should be running on port 1443. You can check with:
* telnet localhost 1443
## Reverse Proxy
Of course, we don't want to expose the service on port 1443. Instead we want our normal webserver to forward all requests to Firefox send ("Reverse proxy").
Of course, we don't want to expose the service on port 1443. Instead we want our normal webserver to forward all requests to Send ("Reverse proxy").
# Apache webserver

6
docs/faq.md
View File

@@ -1,4 +1,4 @@
## How big of a file can I transfer with Firefox Send?
## How big of a file can I transfer with Send?
There is a 2.5GB file size limit built in to Send(1GB for non-signed in users), however, in practice you may
be unable to send files that large. Send encrypts and decrypts the files in
@@ -17,9 +17,9 @@ Many browsers support this standard and should work fine, but some have not
implemented it yet (mobile browsers lag behind on this, in
particular).
## Why does Firefox Send require JavaScript?
## Why does Send require JavaScript?
Firefox Send uses JavaScript to:
Send uses JavaScript to:
- Encrypt and decrypt files locally on the client instead of the server.
- Render the user interface.