Thanks! Good to see what's planned.
If I get the motivation later this Summer, I may do a pull request or two. Although, no promises. It's been about 2 or 3 years since I've done anything with PHP, and I have no experience with Laravel.
I've only worked with Laravel for a year. Never have heard of it until Boom mentioned about it and got me going in the right direction. I put an extensive installation guide in the
readme.
Also, have you excluded music uploads for the same reasons discussed in this thread?
I actually got two reasons. The first is not copyright, but more about the work that needs to be put through to be able to locate blatant copying music. It's perfectly legal to reuse a piece of content, as long as that piece of content is not copyrighted as well.
The second reason is size. Even if images or models might be big, the music is comparable gigantic. I rather disable such a feature mostly for this reason to avoid having to store so big add-ons on the server. Of course, it should be fully possible to enable music if the host think the drawbacks are not that bad. Currently I'm not sure of how I'll put this into play.
Finally, do you plan on making this project something that anyone can easily download to host their own archive, or something that's intended to be provided as a service? I know that it being on GitHub more-or-less implies the former. However, I wonder how much of this will be reflected in your code. For instance, are you planning on adding options for customization?
My host is only there for a general view of how it'll look like. Sure, I wont take it down nor limit it so it can still be used as a normal host. However, the whole thing with this project is to make others take over it whenever they think they want to be a host.
I currently have the general customization for environment variables, but I tend to add more later on to make it easier to use. For now, one can change some of it through the seed files.
Personally, I would love to run something like this locally, but not necessarily publicly.
Laravel is built so you can do local testing in a closed environment, and then put it in production on the server that is public.
