Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.
Please keep in mind:
He answered that @jaakko . It exists. You just need to write the htaccess rules to enable it along with flipping the setting in the link Rodolfo linked.@Rodolfo how about custom domain for each user? Would that be possible?
I meant real domain, not subdomain.He answered that @jaakko . It exists. You just need to write the htaccess rules to enable it along with flipping the setting in the link Rodolfo linked.
It's pretty nice, but it does have a lot of issues. I find it breaks often so I stopped using it. But if you wanna write the htaccess rules go for it.
I don't understand why you want to design a system with that complexity. Each username should be a single personal-mode stand-alone instance.I meant real domain, not subdomain.
I want only one instance but an ability for users to use their own domain. That way it's a lot easier to monetize the service. The same way like you have an option to use Blogger with custom domain.I don't understand why you want to design a system with that complexity. Each username should be a single personal-mode stand-alone instance.
That's not really easily possible with how Chevereto and most server infrastructures are set up. This is a huge networking DNS feat, and you probably should go hire 2-3 IT Guys, 1-2 Software Developers, and a Customer Support agent while you're at it unless you want to set up each one as a network license manually, one by one. You're looking at $320,000 a year without hardware to just pull this feat off on your own.I want only one instance but an ability for users to use their own domain. That way it's a lot easier to monetize the service. The same way like you have an option to use Blogger with custom domain.
But why one installation and not multiple, each one in its own context? That way users could use your service more intensively because they will have their own users and needs.I want only one instance but an ability for users to use their own domain. That way it's a lot easier to monetize the service. The same way like you have an option to use Blogger with custom domain.
I would like to provide a quite simple photo gallery for users, and a lot of storage for them to upload and store original files. I know a Finnish service provider who does that and they make a lot of money. Here is their website translated into English https://translate.google.com/translate?hl=&sl=fi&tl=en&u=https://kuvat.fi/But why one installation and not multiple, each one in its own context? That way users could use your service more intensively because they will have their own users and needs.
I understand the kind of service you want to build, but I don't share the way you are looking to make it happen as you are simplifying on the wrong layer.
If that were the case then how there are one man webhosting providers? With HostBill or WHMCS providing a hosting service is quite easyThat's not really easily possible with how Chevereto and most server infrastructures are set up. This is a huge networking DNS feat, and you probably should go hire 2-3 IT Guys, 1-2 Software Developers, and a Customer Support agent while you're at it unless you want to set up each one as a network license manually, one by one. You're looking at $320,000 a year without hardware to just pull this feat off on your own.
This is hugely complex, to split up Chevereto on a per domain basis automatically. Manually? Sure, it's possible. I suggest you get comfortable with writing htaccess.
URL Masking Using .htaccess | Hostwinds
There are two main types of redirects, temporary and permanent. We will focus on another type of redirect called URL Masking in this guide and review how to accomplish URwww.hostwinds.com
If that were the case then how there are one man webhosting providers? With HostBill or WHMCS providing a hosting service is quite easy
Because language subdomains works best for SEO, it drives way more traffic as language stops being a barrier.@Rodolfo by the way, why are subdomains used for languages? Wouldn't it be easier to to detect user's browser language?
š¤ It works exactly as you describe.If a user wants another language there could be a small menu for changing language and the selection would be stored in a cookie. For logged in users there could be a more permanent setting in their profile.
Read about href Lang šsearch engines doesn't like if you host same content on different URLs.
If you really care about it then consider to post a RFC. https://chv.to/rfc I do have very clear channels for collaboration, hope your feedback doesn't get lost in a post reply.Would be great if V4 had an option to use subdomains for user profiles. I donāt need foreign language users on my site.
What's more profesional? A hostal or a hotel? I believe that an hotel is more pro, I have my own bathroom, bedroom, key... But hey, is just my personal opinion.If user wants to share his profile link it looks more professional to have user.photos.com than photos.com/user