Please report any issues here on GitHub.
-
Check out the latest release from GitHub:
git clone [email protected]:powdahound/s3browser.git -
Assuming you already have the heroku toolkit set up, create an app:
heroku apps:create my-file-browser -
Set the necessary config values:
heroku config:set BUCKET_NAME=my-bucket heroku config:set S3_ACCESS_KEY=xxx # a key with access to perform a bucket object listing heroku config:set S3_SECRET_KEY=xxx heroku config:set PAGE_HEADER=X's Files heroku config:set AUTH0_DOMAIN=mydomain.auth0.com heroku config:set AUTH0_CLIENT_ID=xxx # Your client application id from Auth0 heroku config:set AUTH0_CLIENT_SECRET=xxx # Your client application secret from Auth0 heroku config:set AUTH0_CALLBACK_URL=https://app.mydomain.com # The configured callback URL from Auth0 -
Deploy to Heroku and load the site
git push heroku master heroku open
-
Create an application in Auth0. The application will provide all of the configuration values needed for authentication.
-
Options configurations:
a. Only allow Google logins.
Applications->(application)->Connections
only enable google-auth2
b. Restrict the domains of user email addresses.
Rules->Create Rule->Email domain whitelist
Change the whitelist to your domains.
-
Check out the latest release from GitHub:
cd /srv/www git clone [email protected]:powdahound/s3browser.git -
Add an Apache VirtualHost for your new subdomain. e.g.:
<VirtualHost *:80> ServerName s3browser.example.com DocumentRoot /srv/www/s3browser/www <Directory /> AllowOverride all Order allow, deny Allow from all </Directory> </VirtualHost> -
Tweak config to your liking. Each option is documented in the config.php file. Since it defaults to loading the values from environment variables, using SetEnv is probably best. You could also edit config.php to your liking.
-
Reload your Apache config:
sudo /etc/init.d/apache2 reload