thereverend403 / upste Goto Github PK

View Code? Open in Web Editor NEW

45.0 45.0 8.0 682 KB

A file hosting application with an emphasis on serving technology communities.

Home Page: https://u.pste.pw

License: GNU Affero General Public License v3.0

PHP 76.14% JavaScript 2.49% CSS 0.83% Shell 1.33% HTML 19.22%

upste's People

Contributors

Stargazers

Watchers

Forkers

cloudxtreme zhongfu alesf ariqmuhammadt myang32 vishvega whois-bogeyman veritas44

upste's Issues

FFMPEG video thumbnails.

I noticed from when uploading videos or music, thumbnails from either the id3 artwork or a screenshot of a video wouldn't be seen, instead you'd get the missing thumbnail image. I was thinking what if for videos, it'd generate a lossless png thumbnail from ffmpeg and a set frame. As for music you could retrieve the id3 info with getID3. Also for the thumbnails, would it be possible to have them cropped in, instead of scaled down to fit the 1:1 factor?

API: Delete Function

Does a delete function exist in the API, or copying a delete url? I'm using sharex with an adapted sr.ht script from https://github.com/ShareX/CustomUploaders/blob/master/sr.ht.json and was hoping to add a copy Delete link function to this script.

Trying to get property of non-object

It seems like I'm getting this error. I'm not really sure what triggered it but here's the log.
http://hastebin.com/iwifuranih.tex

Database Migration

I recently updated to the newest version and noticed a new migration "add_email_confirmation.php". Is there anything special that you have to do to apply this? I was thinking of running php artisan migrate but read that it would only reset the DB back to its initial state. Does composer update take care of it?

Retrieve thumbnail through API

I was wondering if it's possible to retrieve the thumbnail through the API for sharex.

ShareX supports $ThumbnailURL on custom uploaders like

"ResponseType": "Text", "URL": "$json:data.img_url$", "ThumbnailURL": "$json:data.thumb_url$",

Would it be possible to use an API function like the deletion one "DeletionURL": "$json:delete_url$" but for the thumbnail?

Bug: Binary Files formatted as .bin

I'm not sure if this is an intended feature change or not but if I say upload a file with the extension .fbx (3D stuff, like for maya), it'll format the url to .bin. It is a binary file but the original extension doesnt appear in the url which could cause confusion when linking items. .exe seems to format just fine (correctly to randomletters.exe even though its also a binary file.

Upload through subdomain

Would it be possible to have all uploads go through a separate subdomain like with a.pste.pw being used for viewing the uploads?

I'm using Cloudflare and their "Maximum Upload Size" is 100MB where I have a 5GB file limit on my nginx/php config. I was hoping to allow users to browse the main site and the a.* subdomain on Cloudflare's network (CDN) and have all uploads go through the subdomain that's not connected to the cloudflare network.

Or if it's possible, is there a way to split the upload into many requests? Cloudflare has a max of 100MB per request, so what if it uploaded it in "parts" and then pieced it together after it's all uploaded?

Also I added a reply to the "Url formatting" issue that I had opened, could you reopen it if possible?

Broken install after trying incompatible PHP version

I might have broken my install of uPste but am unsure if it's requiring a reinstall or can be fixed manually. I've backed up the mysql DB (although didn't think to take one before php upgrade from 7.1 to 7.2). I ran composer update on php 7.2 and think possibly that is what broke packages possibly. Composer possibly getting packages newer than what is supported by 7.1?

 PHP Fatal error:  Uncaught ErrorException: file_put_contents(/path/upste/storage/framework/views/randomnumbersletters.php): failed to open stream: Permission denied in /path/upste/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:111
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'file_put_conten...', '/path...', 111, Array)
#1 /path/upste/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php(111): file_put_contents('/path...', 'Client: <?php e...', 0)
#2 /path/upste/vendor/laravel/framework/src/Illuminate/View/Compilers/BladeCompiler.php(116): Illuminate\Filesystem\Filesystem->put('/path...', 'Client: <?php e...')
#3 /path/upste/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.php(51): Illuminate\View\Compilers\BladeCompiler->compile('/path...')
#4 /path/upste/vendor/larav in /path/upste/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php on line 111

This is what I see when I try loading the main frontend, although file links on the subdomain still work. I plan on doing a clean install to see if it fixes itself, do I just need to backup storage and the mysql DB for restoring? I've tried clearing the cache without any luck.

Resetting password link results in Page not found

When you go to reset your password on the login screen, the email that is sent linking to website.url/password/email/code ends up showing "Page Not Found" in the same style as the down for maintenance when doing composer update. Does this happen for you too? I checked using the u.pste.pw site and it seems to result in the same error 40 - Page not found

Dependencies Conflicting

I am running Centos 7 and after setting upste up a while ago, I was able to update just fine without any issues. Now though I'm running into some NPM issues with I believe incorrect package versions that are trying to be updated. I am not sure what to do since I'd like to update my packages but the mismatched npm ones aren't letting me

[root@server]# composer update
> php artisan down
Application is now in maintenance mode.
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Removing ralouphie/mimey (1.0.1)
  - Installing ralouphie/mimey (1.0.2)
    Downloading: 100%         

  - Removing symfony/yaml (v3.1.4)
  - Installing symfony/yaml (v3.1.5)
    Downloading: 100%         

  - Removing symfony/event-dispatcher (v3.1.4)
  - Installing symfony/event-dispatcher (v3.1.5)
    Loading from cache

  - Removing psr/log (1.0.0)
  - Installing psr/log (1.0.2)
    Downloading: 100%         

  - Removing phpspec/phpspec (2.5.2)
  - Installing phpspec/phpspec (2.5.3)
    Downloading: 100%         

  - Removing symfony/css-selector (v3.1.4)
  - Installing symfony/css-selector (v3.1.5)
    Downloading: 100%         

  - Removing symfony/dom-crawler (v3.1.4)
  - Installing symfony/dom-crawler (v3.1.5)
    Loading from cache

  - Removing symfony/class-loader (v3.1.4)
  - Installing symfony/class-loader (v3.1.5)
    Downloading: 100%         

  - Removing league/flysystem (1.0.27)
  - Installing league/flysystem (1.0.28)
    Downloading: 100%         

  - Removing nikic/php-parser (v2.1.0)
  - Installing nikic/php-parser (v2.1.1)
    Downloading: 100%         

Writing lock file
Generating autoload files
> Illuminate\Foundation\ComposerScripts::postUpdate
> php artisan ide-helper:generate
A new helper file was written to _ide_helper.php
> php artisan ide-helper:meta
A new meta file was written to .phpstorm.meta.php
> npm update
> gulp --production
[00:50:14] Using gulpfile /usr/share/nginx/html/upste/gulpfile.js
[00:50:14] Starting 'default'...
[00:50:14] Starting 'sass'...

Fetching Sass Source Files...
   - resources/assets/sass/global.scss


Saving To...
   - public/assets/css/global.css

[00:50:19] Finished 'default' after 5.39 s
[00:50:22] Finished 'sass' after 8.32 s
[00:50:22] Starting 'sass'...

Fetching Sass Source Files...
   - resources/assets/sass/error.scss


Saving To...
   - public/assets/css/error.css

[00:50:22] Finished 'sass' after 56 ms
[00:50:22] Starting 'sass'...

Fetching Sass Source Files...
   - resources/assets/sass/thumbnailhover.scss


Saving To...
   - public/assets/css/thumbnailhover.css

[00:50:22] Finished 'sass' after 43 ms
[00:50:22] Starting 'styles'...

Fetching Styles Source Files...
   - node_modules/dropzone/dist/basic.css


Saving To...
   - public/assets/css/dropzone.css

[00:50:22] Finished 'styles' after 58 ms
[00:50:22] Starting 'scripts'...

Fetching Scripts Source Files...
   - resources/assets/js/thumbnailhover.js


Saving To...
   - public/assets/js/thumbnailhover.js

[00:50:25] Finished 'scripts' after 3.3 s
[00:50:25] Starting 'scripts'...

Fetching Scripts Source Files...
   - node_modules/dropzone/dist/dropzone.js
   - resources/assets/js/dropzone.js


Saving To...
   - public/assets/js/dropzone.js

[00:50:26] Finished 'scripts' after 1.12 s
[00:50:26] Starting 'scripts'...

Fetching Scripts Source Files...
   - node_modules/jquery/dist/jquery.js
   - node_modules/bootstrap-sass/assets/javascripts/bootstrap/modal.js
   - node_modules/bootstrap-sass/assets/javascripts/bootstrap/transition.js
   - node_modules/bootstrap-sass/assets/javascripts/bootstrap/collapse.js
   - node_modules/bootstrap-sass/assets/javascripts/bootstrap/dropdown.js
   - node_modules/bootstrap-sass/assets/javascripts/bootstrap/alert.js
   - resources/assets/js/global.js


Saving To...
   - public/assets/js/global.js

[00:50:28] Finished 'scripts' after 1.66 s
[00:50:28] Starting 'version'...

Fetching Version Source Files...
   - public/assets/css/global.css
   - public/assets/css/error.css
   - public/assets/js/thumbnailhover.js
   - public/assets/css/thumbnailhover.css
   - public/assets/css/dropzone.css
   - public/assets/js/global.js
   - public/assets/js/dropzone.js
   - public/assets/img/favicon.png <-- Not Found
   - public/assets/img/thumbnail.png


Saving To...
   - public/build

[00:50:28] Finished 'version' after 152 ms
> php artisan migrate
Nothing to migrate.
> php artisan optimize
Generating optimized class loader
Compiling common classes
> php artisan cache:clear
Cache cleared successfully.
> php artisan config:cache
Configuration cache cleared!
Configuration cached successfully!
> php artisan view:clear
Compiled views cleared!
> php artisan route:cache
Route cache cleared!
Routes cached successfully!
> php artisan queue:restart
Broadcasting queue restart signal.
> php artisan up
Application is now live.


[root@server]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.mirror.lstn.net
 * epel: fedora-epel.mirror.lstn.net
 * extras: mirror.5ninesolutions.com
 * remi-safe: repo1.dal.innoscale.net
 * updates: repo.us.bigstepcloud.com
Resolving Dependencies
--> Running transaction check
---> Package MariaDB-client.x86_64 0:10.1.17-1.el7.centos will be updated
---> Package MariaDB-client.x86_64 0:10.1.18-1.el7.centos will be an update
---> Package MariaDB-common.x86_64 0:10.1.17-1.el7.centos will be updated
---> Package MariaDB-common.x86_64 0:10.1.18-1.el7.centos will be an update
---> Package MariaDB-server.x86_64 0:10.1.17-1.el7.centos will be updated
---> Package MariaDB-server.x86_64 0:10.1.18-1.el7.centos will be an update
---> Package MariaDB-shared.x86_64 0:10.1.17-1.el7.centos will be updated
---> Package MariaDB-shared.x86_64 0:10.1.18-1.el7.centos will be an update
---> Package galera.x86_64 0:25.3.17-1.rhel7.el7.centos will be updated
---> Package galera.x86_64 0:25.3.18-1.rhel7.el7.centos will be an update
---> Package kernel-headers.x86_64 0:3.10.0-327.28.3.el7 will be updated
---> Package kernel-headers.x86_64 0:3.10.0-327.36.2.el7 will be an update
---> Package kmod.x86_64 0:20-5.el7 will be updated
---> Package kmod.x86_64 0:20-8.el7_2 will be an update
---> Package kmod-libs.x86_64 0:20-5.el7 will be updated
---> Package kmod-libs.x86_64 0:20-8.el7_2 will be an update
---> Package kpartx.x86_64 0:0.4.9-85.el7_2.5 will be updated
---> Package kpartx.x86_64 0:0.4.9-85.el7_2.6 will be an update
---> Package memcached.x86_64 0:1.4.15-9.el7 will be updated
---> Package memcached.x86_64 0:1.4.15-9.el7_2.1 will be an update
---> Package nodejs.x86_64 0:5.12.0-1nodesource.el7.centos will be updated
---> Package nodejs.x86_64 1:6.7.0-107.el7 will be an update
--> Processing Dependency: npm = 1:3.10.3-107.el7 for package: 1:nodejs-6.7.0-107.el7.x86_64
--> Processing Dependency: libuv >= 1:1.9.1 for package: 1:nodejs-6.7.0-107.el7.x86_64
--> Processing Dependency: libuv.so.1()(64bit) for package: 1:nodejs-6.7.0-107.el7.x86_64
--> Processing Dependency: libicuuc.so.50()(64bit) for package: 1:nodejs-6.7.0-107.el7.x86_64
--> Processing Dependency: libicui18n.so.50()(64bit) for package: 1:nodejs-6.7.0-107.el7.x86_64
--> Processing Dependency: libicudata.so.50()(64bit) for package: 1:nodejs-6.7.0-107.el7.x86_64
---> Package openssl.x86_64 1:1.0.1e-51.el7_2.5 will be updated
---> Package openssl.x86_64 1:1.0.1e-51.el7_2.7 will be an update
---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.5 will be updated
---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.7 will be an update
---> Package python.x86_64 0:2.7.5-38.el7_2 will be updated
---> Package python.x86_64 0:2.7.5-39.el7_2 will be an update
---> Package python-libs.x86_64 0:2.7.5-38.el7_2 will be updated
---> Package python-libs.x86_64 0:2.7.5-39.el7_2 will be an update
---> Package railgun-stable.x86_64 0:5.2.0-1.el7 will be updated
---> Package railgun-stable.x86_64 0:5.3.0-1.el7 will be an update
---> Package systemd.x86_64 0:219-19.el7_2.12 will be updated
---> Package systemd.x86_64 0:219-19.el7_2.13 will be an update
---> Package systemd-libs.x86_64 0:219-19.el7_2.12 will be updated
---> Package systemd-libs.x86_64 0:219-19.el7_2.13 will be an update
---> Package systemd-sysv.x86_64 0:219-19.el7_2.12 will be updated
---> Package systemd-sysv.x86_64 0:219-19.el7_2.13 will be an update
---> Package tzdata.noarch 0:2016f-1.el7 will be updated
---> Package tzdata.noarch 0:2016g-2.el7 will be an update
--> Running transaction check
---> Package libicu.x86_64 0:50.1.2-15.el7 will be installed
---> Package libuv.x86_64 1:1.9.1-1.el7 will be installed
---> Package npm.x86_64 1:3.10.3-107.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

===========================================================================================================================
 Package                      Arch                 Version                                  Repository                Size
===========================================================================================================================
Updating:
 MariaDB-client               x86_64               10.1.18-1.el7.centos                     mariadb                   39 M
 MariaDB-common               x86_64               10.1.18-1.el7.centos                     mariadb                   43 k
 MariaDB-server               x86_64               10.1.18-1.el7.centos                     mariadb                  100 M
 MariaDB-shared               x86_64               10.1.18-1.el7.centos                     mariadb                  1.3 M
 galera                       x86_64               25.3.18-1.rhel7.el7.centos               mariadb                  7.8 M
 kernel-headers               x86_64               3.10.0-327.36.2.el7                      updates                  3.2 M
 kmod                         x86_64               20-8.el7_2                               updates                  114 k
 kmod-libs                    x86_64               20-8.el7_2                               updates                   47 k
 kpartx                       x86_64               0.4.9-85.el7_2.6                         updates                   60 k
 memcached                    x86_64               1.4.15-9.el7_2.1                         updates                   84 k
 nodejs                       x86_64               1:6.7.0-107.el7                          epel                     4.6 M
 openssl                      x86_64               1:1.0.1e-51.el7_2.7                      updates                  712 k
 openssl-libs                 x86_64               1:1.0.1e-51.el7_2.7                      updates                  953 k
 python                       x86_64               2.7.5-39.el7_2                           updates                   89 k
 python-libs                  x86_64               2.7.5-39.el7_2                           updates                  5.6 M
 railgun-stable               x86_64               5.3.0-1.el7                              cloudflare               5.6 M
 systemd                      x86_64               219-19.el7_2.13                          updates                  5.1 M
 systemd-libs                 x86_64               219-19.el7_2.13                          updates                  358 k
 systemd-sysv                 x86_64               219-19.el7_2.13                          updates                   54 k
 tzdata                       noarch               2016g-2.el7                              updates                  440 k
Installing for dependencies:
 libicu                       x86_64               50.1.2-15.el7                            base                     6.9 M
 libuv                        x86_64               1:1.9.1-1.el7                            epel                      79 k
 npm                          x86_64               1:3.10.3-107.el7                         epel                     2.5 M

Transaction Summary
===========================================================================================================================
Install              ( 3 Dependent packages)
Upgrade  20 Packages

Total size: 185 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test


Transaction check error:
  file /usr/lib/node_modules/npm/node_modules/node-gyp from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/doc from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/html from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/man from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/abbrev from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/ansi-regex from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/ansicolors from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/ansistyles from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/aproba from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/archy from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/chownr from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/cmd-shim from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/columnify from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/config-chain from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/debuglog from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/dezalgo from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/editor from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/fs-vacuum from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/fs-write-stream-atomic from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/fstream from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/fstream-npm from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/glob from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/graceful-fs from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/has-unicode from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/hosted-git-info from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/iferr from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/imurmurhash from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/inflight from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/inherits from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/ini from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/init-package-json from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lockfile from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash._baseindexof from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash._baseuniq from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash._bindcallback from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash._cacheindexof from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash._createcache from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash._getnative from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash.clonedeep from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash.restparam from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash.union from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash.uniq from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/lodash.without from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/mkdirp from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/npmlog from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/nopt from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/normalize-git-url from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/normalize-package-data from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/npm-cache-filename from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/npm-install-checks from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/npm-package-arg from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/npm-registry-client from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/readable-stream from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/retry from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/npm-user-validate from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/once from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/opener from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/osenv from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/path-is-inside from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/read from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/read-cmd-shim from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/read-installed from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/read-package-json from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/read-package-tree from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/readdir-scoped-modules from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/realize-package-specifier from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/request from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/rimraf from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/semver from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/sha from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/slide from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/sorted-object from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/strip-ansi from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/tar from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/text-table from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/uid-number from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/umask from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/unique-filename from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/unpipe from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/validate-npm-package-license from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/validate-npm-package-name from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/which from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/wrappy from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
  file /usr/lib/node_modules/npm/node_modules/write-file-atomic from install of npm-1:3.10.3-107.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64

Error Summary
-------------

[root@server]#

activating a user's account should automatically log them in

Text Formatting

Would it be possible to have text formatted where the code would be colored in the way that makes sense depending on the language? Instead of it just appearing as plain text in the browser, it could auto detect the different extensions formatting them properly

Searching Uploads

Would it be possible to add a feature to search through your uploads?

'You didn't supply a file to upload' and 'missing_api_key' for files above 1MB

I am getting the following issues when I try to upload files to the upste. It appears to be when a file is a certain size (1MB or above) that this issue appears. The upload limit is set to 150mb, so this should not be an issue.

Different file formats appear to be fine.

https://pengucloud.moonpengu.in/t9f.png

Any ideas what this could be?

Memory (leak?) Issue in PHP

My php.ini has its memory limit set to 128MB.

I tried uploading a 200MB file and it was uploading up until it "finished" giving out this code in red. Image
http://hastebin.com/etiwonovem.sm
Then I received an email from the system (upste/laravel) saying

Subject: [upload.immo] Application Exception

Client: My IP
URL: http://upload.immo/api/upload

`Symfony\Component\Debug\Exception\FatalErrorException: Allowed memory size of 134217728 bytes exhausted (tried to allocate 275642824 bytes) in /path/to/my/upste/realfolder/app/Http/Controllers/Api/UploadController.php:114
Stack trace:

0 {main}`

I was getting this even before the updates you pushed out today and yesterday.
I looked it up and people were saying that it was probably a memory leak caused by the php script.

on a side note, I added you on steam and you accepted. Could we talk there, it'd be a lot easier with communication than GitHub issues.

PHP 7.2 support

Would it be possible to support PHP 7.2? With 7.1 (max supported php version by Laravel 5.2) ending its active support on the first of next month and ending security updates a year from now it might be risky to keep running 7.1.

Laravel 5.4 is the next version to support 7.2 it seems according to this, 5.3 requirements 5.4 requirements

Link to dates of PHP EOLs

Nginx config

I'm sorry to open another issue so soon after the last but I was wondering how the nginx config works, I'm trying to make it work with my domain, replaced localhost with my domain name and kept the subdomains there, but it's not loading up, even through direct IP. I was just wondering how you set it up since I'm unable to get it working

Cache error

I'm not sure if this was a one time thing or a bug but I think the cache failed to load this one time for 1 client. I uploaded a file to give to them and opened it myself and it worked just fine, but when they opened it up, I started receiving "Application Exception" emails
ErrorException: file_put_contents(/path/to/upste/storage/framework/cache/ee/1e/40characterrandomcodehere): failed to open stream: No such file or directory in /path/to/upste/bootstrap/cache/compiled.php:7366

#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'file_put_conten...', '/path/t...', 7366, Array)
#1 /path/to/upste/bootstrap/cache/compiled.php(7366): file_put_contents('/path/t...', '1469354863i:1;', 2)
#2 /path/to/upste/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php(106): Illuminate\Filesystem\Filesystem->put('/path/t...', '1469354863i:1;', true)
#3 /path/to/upste/vendor/laravel/framework/src/Illuminate/Cache/Repository.php(206): Illuminate\Cache\FileStore->put('cached_view:173...', '1469354863i:1;', 60)
#4 [internal function]: Illuminate\Cache\Repository->put('cached_view:173...', 1, 60)
#5 /path/to/upste/vendor/laravel/framework/src/Illuminate/Cache/CacheManager.php(296): call_user_func_array(Array, Array)
#6 /path/to/upste/bootstrap/cache/compiled.php(6329): Illuminate\Cache\CacheManager->__call('put', Array)
#7 /path/to/upste/app/Http/Controllers/DownloadController.php(28): Illuminate\Support\Facades\Facade::__callStatic('put', Array)
#8 [internal function]: App\Http\Controllers\DownloadController->get(Object(Illuminate\Http\Request), Object(App\Models\Upload))
#9 /path/to/upste/bootstrap/cache/compiled.php(9419): call_user_func_array(Array, Array)
#10 /path/to/upste/bootstrap/cache/compiled.php(9481): Illuminate\Routing\Controller->callAction('get', Array)
#11 /path/to/upste/bootstrap/cache/compiled.php(9461): Illuminate\Routing\ControllerDispatcher->call(Object(App\Http\Controllers\DownloadController), Object(Illuminate\Routing\Route), 'get')
#12 [internal function]: Illuminate\Routing\ControllerDispatcher->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#13 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#14 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#15 /path/to/upste/bootstrap/cache/compiled.php(9938): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#16 /path/to/upste/bootstrap/cache/compiled.php(9462): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#17 /path/to/upste/bootstrap/cache/compiled.php(9449): Illuminate\Routing\ControllerDispatcher->callWithinStack(Object(App\Http\Controllers\DownloadController), Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'get')
#18 /path/to/upste/bootstrap/cache/compiled.php(8517): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'App\\Http\\Contro...', 'get')
#19 /path/to/upste/bootstrap/cache/compiled.php(8504): Illuminate\Routing\Route->runController(Object(Illuminate\Http\Request))
#20 /path/to/upste/bootstrap/cache/compiled.php(8218): Illuminate\Routing\Route->run(Object(Illuminate\Http\Request))
#21 [internal function]: Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#22 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#23 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#24 /path/to/upste/bootstrap/cache/compiled.php(9938): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#25 /path/to/upste/bootstrap/cache/compiled.php(8219): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#26 /path/to/upste/bootstrap/cache/compiled.php(8210): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#27 /path/to/upste/bootstrap/cache/compiled.php(8200): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#28 /path/to/upste/bootstrap/cache/compiled.php(2419): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#29 [internal function]: Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#30 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#31 /path/to/upste/bootstrap/cache/compiled.php(3225): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#32 [internal function]: Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#33 /path/to/upste/bootstrap/cache/compiled.php(9953): call_user_func_array(Array, Array)
#34 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#35 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#36 /path/to/upste/bootstrap/cache/compiled.php(13400): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#37 [internal function]: Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#38 /path/to/upste/bootstrap/cache/compiled.php(9953): call_user_func_array(Array, Array)
#39 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#40 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#41 /path/to/upste/bootstrap/cache/compiled.php(11943): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#42 [internal function]: Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#43 /path/to/upste/bootstrap/cache/compiled.php(9953): call_user_func_array(Array, Array)
#44 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#45 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#46 /path/to/upste/bootstrap/cache/compiled.php(13139): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#47 [internal function]: Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#48 /path/to/upste/bootstrap/cache/compiled.php(9953): call_user_func_array(Array, Array)
#49 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#50 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#51 /path/to/upste/bootstrap/cache/compiled.php(13076): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#52 [internal function]: Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#53 /path/to/upste/bootstrap/cache/compiled.php(9953): call_user_func_array(Array, Array)
#54 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#55 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#56 /path/to/upste/bootstrap/cache/compiled.php(3286): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#57 [internal function]: Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#58 /path/to/upste/bootstrap/cache/compiled.php(9953): call_user_func_array(Array, Array)
#59 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#60 /path/to/upste/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#61 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#62 /path/to/upste/bootstrap/cache/compiled.php(9938): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#63 /path/to/upste/bootstrap/cache/compiled.php(2366): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#64 /path/to/upste/bootstrap/cache/compiled.php(2350): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#65 /path/to/upste/public/index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#66 {main}

MIME type parsing

I was thinking of this for some time now and wanted to ask you if you'd be possible.
I upload a lot of videos and audio files, some are able to play just fine in the browser but some (like wav files) aren't. I was thinking what if, nginx took any file under a.pste.pw that ended in certain extensions (mov, wav, flac, etc) and it would load up an html5 player that could play it. I'm not really sure how it'd all work, if it'd even be possible to replicate the same behavior that direct file playing would happen in the browser but it was something I thought of. It could parse the url into the player and load up the file in a compatible html5/flash player.

Confirmation on API Delete Url

Would it be possible to get a confirmation window for opening delete links from the API? For an extra addition to security?

Registering users not creating database entry

After I register a new user on the upste site, it does not create any new entry in the users table, and so I cannot log in.

I have tried checking the other database related issues listed, but nothing seems to have worked for me.

I am using postgresql, the user I have has been given all permissions related to everything in the postgres database using:

grant all privileges on database dbname to dbuser;

I have successfully used php artisan to create the database schema using the same user details.

Is there anything I am missing? or any ideas as to what could be the problem?

Thanks in advance.

thumbnails broken

I think the last update with changing the file extensions to lowercase might've broken thumbnails.

Merge domain and site_name variable into site_name

In .env, there are two settings: site_name and domain. As far as I can see, site_name is only used in as the title for the index page (when not logged in), and as the sender name in emails sent from uPste. domain, on the other hand, is used to reference the site throughout the web interface and in emails to the user.

I have some minor gripes with this setup:

Referring to the installation of uPste by its name (i.e. site_name) seems more appropriate than referring to by its domain throughout uPste
The name of the domain variable is misleading -- although the attached comment in the config clears that up

Right now, users can simply set both variables to the same value. Regardless, having two different variables to refer to the site is mildly redundant; hence, I suggest that the two variables be merged into a single one, making references to the site more uniform.

Thanks for hearing me out!

(At the very least, using site_name for the navbar title to match the html title would make more sense than using domain.)

SQL issues with setup

I'm trying to set this up on Ubuntu 14.04 with mariadb (drop in replacement for mysql) and haven't had much luck. I changed the info in .env and tried the artisan migrate command but it gave me this error
[PDOException] SQLSTATE[28000] [1045] Access denied for user 'upste'@'localhost' (using password: YES)

I then tried configuring it with the default sqlite settings but it gave me this error
[InvalidArgumentException] Database (/usr/share/nginx/html/upste/storage/database.sqlite) does not exist

I did touch database.sqlite in the storage folder and it finally gave this

Migration table created successfully. [Doctrine\DBAL\DBALException] Operation 'Doctrine\DBAL\Platforms\AbstractPlatform::getAlterTableSQL' is not supported by p latform.

I am not sure how to continue. I'm using PHP 5.5.34-1, MariaDB 10.1.13 (mysql Ver 15.1), nginx 1.9.13, Latest Composer dev version as of today, sqlite 3.8.2, and finally NodeJS version v5.10.0
and NPM 3.8.3.

Apache httpd configuration

I'm trying to set up a httpd configuration to use uPste with but can't get it to work without flaws.
At the same time, I am pretty bad at nginx configuration (as I've never worked with it) :)
This unfortunately leads to me being unable to correctly setup Apache2 for uPste.

May I ask for a textual description of steps needed to get uPste working from a webservice perspective?
I.e., what kind of redirects (or rewrites) do I need in which case and where should they go?
What folders do need which kind of protection?

Thanks and kind regards.

resources scripts hidden behind login

makes it impossible to curl/wget a script, user has to manually copy/paste

Custom CSS changes

I have some custom css changes in the /resources/views/layouts/master.blade.php as well as some changes in the /resources/views/account/resources.blade.php for adding a sharex script

Would there be any way to be able to add a child theme to this to override the default content and have it be as a seperate file so it doesnt conflict with git pulls?

users cannot edit uploaded pastes

the U in CRUD is missing

Sqlite error

I'm not sure if it's due to this probably becoming outdated but I wanted to report an sqlite error I had in case anyone tries to install this

When I try to install uPste with Node 10.3, it ends up failing starting with a github release that is no longer available

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated [email protected]: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated [email protected]: This version is no longer maintained. Please upgrade to the latest version.

> [email protected] install /usr/share/nginx/html/upste/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/linux-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/linux-x64-64_binding.node": 

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g. 

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

> [email protected] postinstall /usr/share/nginx/html/upste/node_modules/node-sass
> node scripts/build.js

So I went back to what CentOS 7 EPEL offers which is node 6.14.3 and 0npm 3.10.10. The install works just fine but if I try to run the next step of creating the sqlite DB I get the following error. Is Sqlite broken you think now in uPste?

> php artisan migrate

                                                                                                        
  [Doctrine\DBAL\DBALException]                                                                         
  Operation 'Doctrine\DBAL\Platforms\AbstractPlatform::getAlterTableSQL' is not supported by platform.

Open registration option

Would it be possible to have as like a toggle option to have open registration? No admin approval required? Also thanks for adding user preferences, really nice thing there. I was thinking what if you did the same but for admin preferences, and you could change the same options if not more from the .env inside the panel. Lastly, with this new update, it seems to have fixed my php 503 error problem so thanks on that too.

Url formatting

Would it be possible to change the way a url is formatted? I was thinking if the url structure would be something like a.example.com/camjac251/originalfilename.extension and if they are uploading the same filename then it'd format it like a.example.com/camjac251/2/originalfilename.extension
Or if that's not possible, would saving work as when you hit control s in the browser, it'll give you the original filename instead of the random characters like how puush does it or NotPomf (github).

Views update delay

Views on files aren't seeming to update. They were the other day but that was after a few hours of it being up. Is there any way in having views logged instantly?

no API support for full CRUD

ideally, I'd hope the API would allow the user to

upload new files
get a list of all files
update files
delete files

currently only supports the first

thereverend403 / upste Goto Github PK

upste's People

Contributors

Stargazers

Watchers

Forkers

upste's Issues

0 {main}`

Recommend Projects

Recommend Topics

Recommend Org