At the moment, readme instructs users to install MySQL to get pomf to function (though mentions other databases may work).

MySQL, or any full SQL server, is completely unnecessary (though of course there's nothing wrong with using it) for something like pomf. It is an unnecessary dependency, and complicates installation. Many might lazily set it up, leaving it in a potentially insecure configuration.

SQLite is completely self-contained, and requires no configuration. The only change necessary to the code, would be changing the placeholder references to a MySQL server/database in settings.inc.php, to a suitable URI pointing to a location for the SQLite database file.

All copy buttons except the first one don't work in chromium 51.0.2704.84 (Developer Build) (64-bit). When clicked they return the error 'Discontiguous selection is not supported.(anonymous function) @ pomf.min.js'

Supporting upload through netcat on a separate port, like http://termbin.com/ does would be great to allow uploads from unixy systems without additional dependencies.

https://github.com/pomf/pomf-php/blob/master/classes/UploadedFile.class.php

This is not horribly difficult to do. There are two components

• replace SHA-1 with SHA-2 in above
• replace all existing hashes in DB with new one

The latter would be CPU intensive, so running it may need to be planned (and ensuring it has low nice value, etc). It should not be very difficult to generate new hashes in the background, then when ready, use new code that checks SHA-2 hashes.

~~- makes SQLite 3 the default database engine~~ (contentious, so i separated from this PR)

• adds SQLite schema in addition to MySQL one
• readme now includes instructions on how to setup SQLite DB
• readme now includes migration instructions

See discussion at #11

I just saw a original filename with single quotes around it so the extension ended with a single quote

originalfilename: 'filename.ext' filename: asdfe.ext'

not sure this is desired, just bringing it to your attention.

(squashed commits on previous one so can't reopen)

• Previously min-js would continually append to the file with @echo "// @source https://github.com/pomf/pomf/tree/master/static/js" >> ./dist/pomf.min.js (note the >>).
  Fixed so that it overwrites the file whenever it is run now.
• generally made a number of changes so Makefile better follows conventions
• added uninstall support as per Makefile conventions
• added DESTDIR support -- allows specifying installation destination directory in standard Makefile way
• added dist support -- allows archive containing the "compiled" site to be produced via make dist
• replaced program names with the appropriate variables as per makefile conventions
• mkdirs was renamed to installdirs as per makefile conventions
• copy was renamed to install for the same reasons
• added clean and uninstall targets

It's probably been documented somewhere and asked before, but what can I do to prevent random people from uploading to my private pomf? I'd prefer an api or user/password solution if possible that is compatible with ShareX.

Thank you.

It was a shitty implementation and would even require a re-write of moe to make it work.

Suggest we remove it altogether as I don't know any clone who would bother with it.

See: #11 for discussion; #17 adds schema and instructions without making SQLite the default

• has zero impact on already set up sites
• at the moment all MySQL settings in settings.inc.php are placeholders
• MySQL requires substantially more setup than SQLite
• SQLite simplifies pomf set up
• instructions on how to set up SQLite (very simple) are covered in #17
• no instructions on setting up MySQL provided

• makes SQLite default database in settings.inc.php
• adds SQLite schema in addition to mysql one
• readme now includes instructions on how to setup sqlite DB
• readme includes migration instructions

this feature of mine is made out of cobbled together spaghetti and tears, clipboard grabbing needs a rewrite to latest mozilla suggestions, and the HTML elements desperately needs to be redone to something that doesn't looks horrible and makes me cry everytime i upload to a clone.

The actual pseudo code itself is sound, but our implementation is certainly not the best

Hello all,

Installed both Pomf and Moe, both work fine. However, when trying to upload a file (.jpg, .png, etc), I receive the following error:

Cant read settings file.

I have already checked permissions and have done as said in the documentation. Not sure where to go from here.

chown www-data:www-data /var/www/db
chown www-data:www-data /var/www/db/pomf.sq3
chown www-data:www-data /var/www/files
chmod 775 /var/www
chmod -R 775 /var/www/

Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please merge this PR and migrate to GitHub-native Dependabot before then.

Dependabot has been fully integrated into GitHub, so you no longer have to install and manage a separate app. This pull request migrates your configuration from Dependabot.com to a config file, using the new syntax. When merged, we'll swap out dependabot-preview (me) for a new dependabot app, and you'll be all set!

With this change, you'll now use the Dependabot page in GitHub, rather than the Dependabot dashboard, to monitor your version updates, and you'll configure Dependabot through the new config file rather than a UI.

If you've got any questions or feedback for us, please let us know by creating an issue in the dependabot/dependabot-core repository.

Learn more about migrating to GitHub-native Dependabot

Please note that regular @dependabot commands do not work on this pull request.