Skip to content
Web-based S3 bucket browsing tool. Similar to Apache-style indexes.
PHP ApacheConf
Find file
Latest commit 76c413a Apr 8, 2016 @powdahound Merge pull request #8 from ad-m/endpoint-support
Update S3.php, added custom endpoint
Failed to load latest commit information.
www Update S3.php, added custom endpoint Apr 6, 2016
.gitignore Ignore .env Mar 29, 2016
LICENSE MIT license Feb 29, 2012
Procfile Heroku-ify Jan 11, 2015
README.md Add `heroku open` to instructions Jan 11, 2015
composer.json Heroku-ify Jan 11, 2015
composer.lock Heroku-ify Jan 11, 2015

README.md

Amazon S3 Directory Browser

Please report any issues here on GitHub.

Installation on Heroku (preferred)

  1. Check out the latest release from GitHub:

    git clone git@github.com:powdahound/s3browser.git
    
  2. Assuming you already have the heroku toolkit set up, create an app:

    heroku apps:create my-file-browser
    
  3. 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
    
  4. Deploy to Heroku and load the site

    git push heroku master
    heroku open
    

Installation on Apache

  1. Check out the latest release from GitHub:

    cd /srv/www
    git clone git@github.com:powdahound/s3browser.git
    
  2. 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>
    
  3. 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.

  4. Reload your Apache config:

    sudo /etc/init.d/apache2 reload
    
Something went wrong with that request. Please try again.