Would it be possible to add a type of cdn/mirroring/proxy option to this extension?
Example, upload pictures to another server other than where the flarum forum is actually installed and then make the image links point directly to that said server?

This would be useful for people that need their community to upload a large quantity of images onto the forum so it would be best to just have another server just to store and serve those images so that everything loads super fast.

    Mount remote fs into upload directory?

      VIRUXE Would it be possible to add a type of cdn/mirroring/proxy option to this extension?

      Using the local adapter this is possible by setting a CDN Url. We haven't implemented to assist further on that account.

      7h3ev1l Mount remote fs into upload directory?

      You can do whatever remote mounting with the local adapter.

        7h3ev1l from gitter (please don't post in multiple channels ?):

        The local adapter is that images are saved in the flarum directory

        would it be possible to add an overlay of some kind as an option if we tag an image or post with a "nsfw tag" or smth?

        6 days later

        POST https://xxx.x/api/extensions/flagrow-image-upload

        <br />
        <b>Fatal error</b>: Class 'Flarum\Database\AbstractMigration' not found in <b>/srv/users/serverpilot/apps/xxx/public/vendor/flagrow/flarum-ext-image-upload/migrations/2016_01_11_000000_create_flagrow_images_table.php</b> on line <b>18</b><br />

        Hell what?

          7h3ev1l we need to update the extension to beta5. We'll do it in the following days.

          7h3ev1l the migrations for most of the Flagrow extensions have been readied, we need to fix the frontend constraints and test before releasing. Sadly I'm not fully available right now, we're aware this needs fixing and will do so as soon as humanly possible.

          I fixed it .. edit this file:
          /vendor/flagrow/flarum-ext-image-upload/migrations/2016_01_11_000000_create_flagrow_images_table.php
          with:

          <?php 
          namespace flagrow\image\upload\Migration;
          
          use Flarum\Database\Migration;
          use Illuminate\Database\Schema\Blueprint;
          
          
          return Migration::createTable(
              'flagrow_images',
              function (Blueprint $table) {
                      $table->increments('id');
                      $table->integer('user_id')->unsigned()->nullable();
                      $table->integer('post_id')->unsigned();
                      $table->string('file_name')->nullable();
                      $table->string('upload_method');
                      $table->timestamp('created_at');
              }
          );

            7h3ev1l It might be better to just submit a PR to the Flagrow team at their Image Upload Github page. Then users can install through composer like normal. I don't think most users are going to be comfortable manually editing files to make the extension work.

            Do you know I could get rid of this?

            Whenever I try to uninstall either, I get a 500 error.

              Just tagged version 0.2.0 which makes the extension compatible with Flarum 0.1.0-beta.5. Please let us know if you encounter any issues.

              Tagged 0.2.1 with the German translation, thank you Reflic.

              Is this:
              "General preferences
              Maximum file size (in kilobytes)"
              is for imgur too>?

              Lol i just updated and now i cant upload images to imgur ?

              I tried to reinstall it but still cant upload..

              Huh lol.. after few seconds its working but i dont get uploading progress.

              I am sorry...
              I am having issues using the latest version in the new beta...
              Using local storage the uploads fail.
              Debug Info:

              POST https://domain.com/forum/api/image/upload
              
              {
                "errors": [
                  {
                    "status": "404",
                    "code": "route_not_found"
                  }
                ]
              }
              

              Thank you in advance for any help you might be able to provide. =)