diff options
author | Matěj Cepl <mcepl@cepl.eu> | 2020-01-02 21:23:16 +0000 |
---|---|---|
committer | Matěj Cepl <mcepl@cepl.eu> | 2020-01-02 21:23:16 +0000 |
commit | 5e1b5fe911d4805133357e329d009f998300867d (patch) | |
tree | dff1a7d12784fa9cf689452f0a122c14c3c63550 /doc | |
parent | adee3a503a9b07a73676e65df3af2c9abc8f2acf (diff) | |
parent | 320908419788ca67f81cb869bed7249dab1be8a4 (diff) | |
download | bugseverywhere-5e1b5fe911d4805133357e329d009f998300867d.tar.gz |
Merge branch '2dd5488e-2053-4a16-a853-d7cc7bd48831' into 'master'
Remove serve-storage and HTTP storage driver
See merge request bugseverywhere/bugseverywhere!10
Diffstat (limited to 'doc')
-rw-r--r-- | doc/tutorial.txt | 26 |
1 files changed, 3 insertions, 23 deletions
diff --git a/doc/tutorial.txt b/doc/tutorial.txt index 443ac2a..3a1b8e8 100644 --- a/doc/tutorial.txt +++ b/doc/tutorial.txt @@ -372,33 +372,13 @@ BE over HTTP ------------ Besides using BE to work directly with local VCS-based repositories, -you can use:: - - $ be serve-storage - -To serve a repository over HTTP. For example:: - - $ be serve-storage > server.log 2>&1 & - $ be --repo http://localhost:8000 list - -Of course, be careful about serving over insecure networks, since -malicous users could fill your disk with endless bugs, etc. You can -disabled write access by using the ``--read-only`` option, which would -make serving on a public network safer. - -Serving the storage interface is flexible, but it can be inefficient. -For example, a call to ``be list`` against a remote backend requires -all bug information to be transfered over the wire. As a faster -alternative, you may want to serve your repository at the command -level:: +you can serve your repository over HTTP at the command level:: $ be serve-commands > server.log 2>&1 & $ be --server http://localhost:8000 list -Take a look at the server logs to get a feel for the bandwidth you're -saving! Serving commands over insecure networks is at least as -dangerous as serving storage. Take appropriate precautions for your -network. +Serving commands over insecure networks can be dangerous. Take +appropriate precautions for your network. Driving the VCS through BE -------------------------- |