Access and accounts
This is where the credentials live. They belong to the device and apply to all events. What a party does with them is set with the event: under Cloud and e-mail and Pay-per-use.
The split has a practical reason: an event package handed on never contains credentials. Sending an event as a template does not send your Dropbox account with it.
Cloud account#
Dropbox, Google Drive, pCloud, Nextcloud and the RAWCaptureBooth self-hosted server are supported.
Signing in runs through the browser: an assistant opens the provider's authorisation page, access is confirmed there and the code is carried back into the booth.
A base folder can be set as well. Every event creates its own folder underneath, named after its identifier.
pCloud#
An ordinary cloud account, set up like Dropbox: click Connect to pCloud, confirm in the browser, done. Whether the account lives in the European or the American data centre is detected automatically — the choice made when creating the account has no effect here.
Base folder and folder for the single-image QR codes work as with Dropbox. If left empty, the folder RAWCaptureBooth is created with Einzelbild-QR underneath.
Nextcloud#
Worth it for anyone already running their own Nextcloud: the images stay in-house and the sharing links for the QR codes are created there automatically — a root URL as with the FTP server is not needed.
All that is required is the Nextcloud address, the same one used to open it in a browser. A click on Connect to Nextcloud opens the sign-in page; after confirmation RAWCaptureBooth receives its own app password. The account password itself is never stored, and the app password can be revoked individually in Nextcloud at any time without touching the account. Disconnect withdraws it from here as well.
No separate app has to be registered in Nextcloud. The route works with every installation, even behind a portal that allows no redirect back to the booth computer — unlike Google, the sign-in can therefore also be done from a tablet.
Base folder and folder for the single-image QR codes work as with Dropbox. If left empty, the folder RAWCaptureBooth is created with Einzelbild-QR underneath.
FTP server#
Useful where a web space already exists and the pictures are meant to live under your own address instead of a cloud provider's. Two entries are needed that are easily confused: the base folder on the server — the path the FTP account sees — and the root URL — the address under which exactly this folder is reachable on the web. Both point at the same place but rarely carry the same name: /httpdocs/photos on the server may be https://example.com/photos on the web.
FTP, FTPS and SFTP are available as protocols. FTP transmits password and images in clear text; where the provider allows FTPS or SFTP, those are the ones to choose.
The folder for the single-image QR codes can be chosen freely. If the field stays empty, a subfolder below the base folder is used. If the chosen folder sits beside the base folder instead of below it, the root URL does not reach it; its own address has to be entered as well. The admin area says so while it is missing.
An access that has been set up can be removed again with the Remove FTP access button. It only appears while something is stored and clears server, user name, password, folders and addresses in one step. Emptying the fields is not enough: an empty password field means “keep the existing password”.
RAWCaptureBooth self-hosted server#
Your own web server hosting the web photo album. It needs the server URL and, if the server asks for them, a user name and password. Which event folder is meant follows from the event's access code, so that code lives with the event rather than here.
A server that has been entered can be removed again with the Remove self-hosted access button. It only appears while something is stored and clears address, user name and password in one step. Emptying the fields is not enough: an empty password field means “keep the existing password”, and an empty server URL is rejected when saving.
Mail access (SMTP)#
The outgoing mail account the booth sends through: host, port, user name, password and encryption (STARTTLS or SSL/TLS). One account for all events.
Payment provider#
The Stripe key — one account for all events. Leaving the key field empty keeps the key already stored. A restricted key works as well as the secret key.
Amount, trigger and flow of the payment are set with the event.
No webhook is needed: the photo booth asks Stripe itself for the state of a payment. PayPal, Apple Pay and Google Pay are switched on as payment methods in the Stripe account; nothing needs to be set at the photo booth for that.
Demo mode only simulates the payment and works without a Stripe account. For a real test run a test key is the better choice, see Pay-per-use.