Open hfiguiere opened 12 years ago
Well, the possibility to manage different subdomains would be a way to manage various users without worrying about subdomains.
There's two issues here. The first is a user wants to install OpenPhoto into a subdirectory. The conflict here is that if the host and path is fixed, then supporting multiple users is not doable (per the current design). IDs for every object are namespaced to the user. So if you want to install into a subdirectory and support multiple users then you're going to have to have directory Alias
es or something similar. That's a hack and doesn't provide much benefit over using subdomains.
So for this issue let's focus on a single user installation into a subdirectory. If we want to discuss the other, we should probably move that to the Google Group since it would require a bit of discussion. http://groups.google.com/group/openphoto
+1 on the "install OpenPhoto into a subdirectory"
For the sake of documentation here is a blog post that outlines the original reason subdirectories weren't supported. http://blog.theopenphotoproject.org/post/10537443380/namespacing-the-web-for-your-photos
Being able to run openphoto inside a subpath would indeed be great.
+1 this is a must have for single user setup with multiple systems on one site like /blog, /photos, /wiki ...
+1
+1
echoing @davidak, without being able to install to a subdirectory, it's very hard to run multiple services from the same server. Subdomains is a reasonable idea, except that for a self-hosted local network setup, that will require editing the hosts
file on every machine, which isn't really sustainable. And if you control the domain name, then you should also be in control of the subdirectories (re @jmathai 's comment/blog post link)
Thanks for the upvotes on this. Just an update from my side.
We don't yet have any immediate plans to add this. I imagine that the effort to enable this is decent but mainly because it probably touches a few parts of the code. For someone familiar with the code I don't think it'd be too difficult (testing would be the most work).
+1 but for an as yet unmentioned reason: SSL. Wildcard certs still cost more. It's good to at least have the option of a free StartSSL cert for a personal gallery.
Same reason here: SSL
I'm quite new to this project, whats the status on this issue?
Nothing new on this issue. To be honest it's not a high priority for the core team.
Per my comment above is there anyone interested in taking on this work?
Currentl openphoto assume it is the top level directory. But this might not be what one want.
We should ensure that openphoto can be installed as a subdir. Like http://mydomains.invalid/gallery/
The know issue is the way we load the config file, currently based on the hostname: this is not good as you should be able to have several instance on the same host with different configs.