Hacker News new | ask | show | jobs
by adestefan 4342 days ago
> nemex doesn’t need a database. This means that you can easily download the zipped package, fire up your ftp-client of choice and copy the files to any directory on your web server. As soon as you successfully uploaded them, navigate to the /projects folder and set the permissions to 777. Open config.php in your nemex-folder and change USERNAME and PASSWORD to anything you want.

Ugh.

3 comments

In 2014 a lot of us don't use shared servers anymore. Personally, for someone like me, throwing this up in my dokku sounds great. I don't think this is designed for the Enterprise.
Agreed that this is ugly. This project would make so much more sense if it were developed as a static site. I haven't looked at the codebase, but if it doesn't require a DB, can it not be ported to Jekyll or Pelican or so? Then it would be extremely easy to host it on S3 for peanuts..
Dynamic project as a static site. Oh RLY? It would be so useful then.
What's wrong with that?
He doesn't like it. Me neither. 777? Too liberal, really not needed. Username and password on a configuration file? Ugh.
The app needs write access to the /projects folder. Many shared hosts need 0777 because PHP runs as a different user than FTP. If you know what you're doing, you can always set it to the minimum required permissions.

What's wrong with the username and pass stored in a config file? Almost all PHP apps store their database credentials in a config.php as well.

I don't get it. 0777 is already the broadest permission you can give. So what is this minimum required permission?

I haven't done much FTP or shared hosts since, maybe, 7-8 years, but I remember Wordpress has the same 0777 is bad practice for many years and hasn't changed.

777 is never a good option.

[1]: http://codex.wordpress.org/Changing_File_Permissions#Shared_...

Anyway, these days, for a couple dollars you can have a really really good cloud hosting service.