Hacker News new | ask | show | jobs
by IanCal 3822 days ago
So first off, it's always cool to have built and released something, so congrats on that, but these are the questions I'm left with as a potential user:

1. What's different about this setup? What can I do that I either can't with a standard webserver setup or would be more cumbersome that way? 2. Why "files within files", what's different about that compared to directories and index files?What can I do that I either can't with a standard directory structure or would be more cumbersome that way?

If I wanted plain text at the moment + scripts, any standard webserver + CGI would give me that right now and I could host it immediately on a large number of hosts (or on my own). So for people like me who would go "ooh, plain text and unix sounds nice" it'd be good to see a set of reasons why what we'd currently do would be improved using this.

1 comments

I'll try my best to answer you. 1. I believe you can do it with a standard webserver setup. But when you want to share scripts and files to other users I believe it would just become a bit more cumbersome. 2. For me files within files is a lot more easier. It is not possible to add comments to directories. When you create a directory its just a string. It is not easy to add extra information to the directory itself. I may be wrong.

Again a webserver+CGI would definitely work no doubt. The app just simplifies it for you. Its the same thing with content management system. Its simpler to use them rather than build it manually. Also I plan to add the ability to share files.

Could you elaborate a bit on "files within files"? I don't think there's an example of that on the page.

You allow people to execute scripts on your server? How does the security aspect of that work?