A fork of the Icarus Imeji Uploader Service tweaked for better compatibility on Caddy webserver.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
YandolsZX 758d095aa4 Updated README.md with Caddy Server instructions. 2 months ago
assets Move droploader files from addonstyle into assets folder. 1 year ago
legacy Added legacy uploader redirector. 1 year ago
public Made public/index.php the 404 page because of how Caddy works. 2 months ago
.gitignore Added .gitignore file. 1 year ago
LICENSE.md Removed apache .htaccess files. 2 months ago
README.md Updated README.md with Caddy Server instructions. 2 months ago
dropload.php Cleanup. 1 year ago
failed.php Also apply assets path change to the upload failed page. 1 year ago
favicon.ico Import current version to date onto the dev server repository. 2 years ago
index.php More cleanup + changes to the legacy front-end. 1 year ago
legacy.php Fixed a domain change missed by the migrationdev branch. 1 year ago
logs.php Changed more filepaths and URLs that I forgot to change. 1 year ago
removal.php Changed more filepaths and URLs that I forgot to change. 1 year ago
robots.txt Updated robots.txt file. 1 year ago
tos.php Changed more filepaths and URLs that I forgot to change. 1 year ago
upload.php Changed hour-base identifiers to intervals of 4 hours instead of 6. 1 year ago

README.md

Icarus Imeji Uploader Service (Caddy Version)

Note: This version of Imeji is modified to run on Caddy. For the Apache version, visit this project instead.

Imeji (for short) is a form of PHP image uploader system that you can use to host a simple image uploader service on your server. It utilizes the dropzone.js library and also includes a basic POST uploader for clients incompatible with the aforementioned dropzone.js library.

This repository is used for development and project tracking of the code we use on our live image uploader. However, you a free to download a copy of it for yourself and alter it to use within the limits of our license.

Requirements

  • A server running Caddy Webserver v2
  • The ability to use subdomains
  • PHP 7.1 or greater

That's about it.

Application Configuration

You can configure parameters within dropload.php and upload.php to your liking, making them both have the same changes or have them function with different parameters respectively.

Anything else such as the front-end design of pages is completely up to you to change. Be sure to change the paths of elements and assets in the index.php file and other related files too.

Caddyfile Configuration

Unlike the Apache version of Imeji, the Caddy version has to be configured differently and is all done from within your Caddyfile instead of a file in the root directory of the application.

Entry file for Imeji Frontend (Users upload images here)

The following is an example Caddyfile entry you can use for the Frontend side of your own Imeji instance, configure it to your specifications.

# Imeji Frontend (User Uploader)
imeji.yandols.xyz {
   root * /path/to/your/imeji
   file_server
   php_fastcgi unix//run/php-fpm/www.sock
   log {
      output file /path/to/your/logs/directory/imeji_frontend.log
      format logfmt
   }

}

Entry file for Imeji Backend (Users are served images here)

The following is an example Caddyfile entry you can use for the Backend side of your own Imeji instance, configure it to your own specifications.

# Imeji Backend (Image File Serving)
i.yandols.xyz {
   root * /path/to/your/imeji/public
   file_server
   php_fastcgi unix//run/php-fpm/www.sock
   header +Access-Control-Allow-Origin "*"
   log {
      output file /path/to/your/logs/directory/imeji_backend.log
      format logfmt
   }
}

Adding a login requirement to access log files

By default, Imeji logs uploads to the uploads.log file, which can be viewed as a sorted table by accessing imeji.yourdomain.com/logs.php in your browser. The log contains sensitive information such as the IP Address and User Agent of the users who upload images to your Imeji instance, so it would be ideal to protect these files behind a login prompt so only authorized users can access them.

Caddy supports the basicauth directive which is one of the ways you can use to protect your logs from unauthorized access.

The following contains an example of the basicauth directive you can add to your Caddyfile entry for the Imeji Frontend. Follow the official Caddy instructions on how to get your password in a hashed form like in the example below. Do NOT use a plaintext password as it will not be accepted by Caddy.

   basicauth /*.log {
      Yourusernamehere JDJhJDEwJEVCNmdaNEg2Ti5iejRMYkF3MFZhZ3VtV3E1SzBWZEZ5Q3VWc0tzOEJwZE9TaFlZdEVkZDhX
   }
   basicauth /logs.php {
      Yourusernamehere JDJhJDEwJEVCNmdaNEg2Ti5iejRMYkF3MFZhZ3VtV3E1SzBWZEZ5Q3VWc0tzOEJwZE9TaFlZdEVkZDhX
   }

Contributing

You can use our issue tracker to help report problems or suggest enhancements on the Imeji system. Pull requests are also welcome.

License

See the LICENSE.md file.

Third Party Code Attribution

  • The Icarus Imeji Uploader Service uses the dropzone.js library by Matias Meno. (MIT License)
  • The front-end template uses the Identity template by ajlkn. (CCA 3.0 License)