Noob poster: I'm trying to set up a Joomla 4 site with four distinct functions 1) Blog 2) Social 3) Mobile and 4) Site development. I plan to add the Gantry 5 framework and Gantry 5 Helium template. Each site function has to share data bidirectionally with the others (e.g. signon and workflow). I have a hosting provider and have been conversing with the hosting techs. There seems to be no definitive answer on whether to set up subdomains or use subdirectories for each of the functions. To lessen the impact of higher volume potential and a contained workflow I was favouring the subdomain route. On this approach the last word was I needed to install Joomla on each subdomain, followed on each by the Gantry 5 framework and then the Gantry 5 template. There appear to be pros and cons on each approach and we haven't been able to determine if subdomains or subdirectories would ultimately give me what I need. The tech suggested I post here. NOTE: There is no additional cost from my provider for using subdomains.
Activity so far: Reading what I can find on subdomains and subdirectories. I'm a designer so I've been reading then conversing then more reading then more conversing with the hosting techs trying to figure out the best way of going. It's taken a few days and now I'm chasing my tail.
Thanks.
Related
I am starting a new career as a developer and I am trying to offer my services to shops in my area for free to use as my portfolio. My question is, is it okay to deploy/hand off a website to my client using google domains and GitHub pages? Since it is the cheapest way to deploy a website?
What is the downside of doing so, or should I just suggest using a hosting site such as Hostgator?
I have created a website that is ready to be handed off.
Here are my thoughts:
For a simple static website that doesn't have server-side scripting (such as PHP, etc.) GitHub pages are a fine route for deploying your website.
Another factor to take into account would be the GitHub pages limits.
No larger than 1 GB
Bandwith limit of 100 GB per month
Limit of 10 builds per hour (excluding custom actions workflows)
Other options
AWS
Google Cloud
Heroku
"I am trying to offer my services to shops in my area for free to use as my portfolio."
Based on this alone, I will tell you that GitHub pages are probably the most ideal way to go for a portfolio. If your website is more complex, however, I would go for one of the options I listed above. Since GitHub pages is free and very easy to use, though, I do recommend it. Say your website grows in complexity and you begin to feel you need more wiggle room/flexibility to control how it's hosted, you can always start using something else.
I would personally, at the very least, use GitHub pages as a starting point for a static site.
I'm a member of a small society with an html website (cmyf.org.uk) built many years ago -most of the information is static and very rarely edited but we would like to add blogging and other functionality. My question is, should we set up a CMS site under a new domain name, or is there a way to combine the existing static site and a new section with modern CMS under the same domain name, without needing to import existing content into the new CMS? We are working with a very small budget so would like to save on domain hosting costs.
You can easily create a dedicated subdomain, i.e.blog.cmyf.org.uk, and set up any cms just for blogging purposes (e.g. WordPress or Ghost CMS). Ask your domain provider or server admin for help - by definition creating and configuring a subdomain is free (in comparison to registration a new domain).
Most of the common off the shelf CMS/blogging software can be relatively easily configured to run from a subdirectory under the webroot.
That would be one way to have both sites co-exist happily, on the same webhosting package and domain.
There may well be other or more desirable ways to accomplish the same thing but they all depend on the details (which software/blogplatform, what webhostingcompany and what kind of features they offer, etc.)
My company has a Kentico v11 site with 6 subdomains. We are planning on adding about 5 more in the near future. The site is made up of one Kentico instance and one set of pages to be served. We simply change the styling of the site based on the subdomain, and we filter the data to only show the appropriate information per subdomain. Up until now, we have been getting a new Kentico license for each subdomain but, that is getting a little burdensome. My question is this: Do we need to get a separate license for each subdomain? If we don't, then how do I avoid the licensing error when I try to access a new subdomain on the site?
Thanks in advance for whatever information you can provide.
You are already following the correct procedure, generating a new license for each subdomain.
I would highly recommend that you discuss anything license related directly with Kentico Xperience sales (sales#xperience.io) or with your account manager.
Kentico 11 support ends on November 30, 2021, I would recommend upgrading your installation to Kentico 12 so you have extended support through fall 2023.
Okay, here's the situation. I've had a bluehost account for several years and am happy enough with it I'm unwilling to move without a really good reason. However, I'm finding more and more that the best solution to the main use for one of my domains is to have a fairly simple rails app running to cover that.
The rails app could easily be front-ended by two forms on the landing page, each with a couple of follow-up pages, but I want the URL always to show "mysite.com" rather than "myapp.heroku.com". I also want to continue to use my email addresses with this site. I don't expect the app to see heavy usage, and am unlikely to go over the 750 hr/mo free time on heroku.
I currently use Rails 3, and would likely have trouble stepping back to rails 2 in my thinking. I'm also not very good at programming in rails, or anything else for that matter, so I'd like not to confuse myself any more than necessary.
So what's my solution here? Transfer the whole domain to Heroku? Embed partials of the app in the landing page? Can I keep email addresses working with Heroku? Can I transfer just the www.mysite.com to heroku, but have everything else involved with the domain hit bluehost?
I'm open to advice.
Heroku doesn't provide any email hosting/sending itself - so you either bring your own or use one of the Heroku addons like SendGrid for sending mail from your application.
Of course, you can just leave you email etc with Bluehost provided that you can modify the DNS and change your www record to be a CNAME to proxy.heroku.com (after you've added the custom domain addon to your Heroku application)
I just did this with blue host and heroku where I hosted my app on heroku and wanted to keep email on blue host. I am using DNS Made easy so your mileage may vary but I had to create an A record pointing to the ip address 69.89.31.63, you name the A record mail.yourdomain.com
and then create an mx record pointing to 69.89.31.63. I am on the cedar stack.
I need advice.
I inherited a website that's been around a long time. The website gets a lot of organic traffic from Google. The business and website owner is upgrading the site to make the content more manageable. At the moment, a wordpress CMS powers half the site. Physical html pages make up the remainder of the site. Here's a summary:
1) Guide section which consists of a php wordpress driven blog found at http://mysite.com/guide. Individual pages in the guide section have urls such as http://mysite.com/guide/4930-hello-world or http://mysite.com/guide/489-welcome-to-my-site. The business owner spent 2 months populating these pages and is reluctant to scrap it for another system.
2) E-commerce section which consists of a thousand static/physical product pages. The product pages are NOT dynamically driven and no url rewrite rules are involved. The pages have urls such as http://mysite.com/products/239123-sofa.html and http://mysite.com/products/23-office-desks.html
The owner wants to use a non-PHP ERP or CRM solutions to power the website's e-commerce section and streamline some of the business' accounting, inventory, marketing and work-flow operations.
I have never worked with ERPs or CRMs before. Some questions I have are:
1) Is it a good idea to have one website under one domain driven by two different technologies? Wordpress manages pages such as http://mysite.com/guide/4930-hello-world while a Microsoft application manages pages such as http://mysite.com/products/239123-sofa.html. As mentioned earlier, the business owner is reluctant to scrap wordpress because he put considerable effort into populating it.
2) What challenges will I experience implementing url-rewrite rules (because it's two technologies under one domain, but different sub-directories)? I need to make sure the website retains its Page Rank and SEO goodies.
3) What server configuration challanges will I experience?
I've never replaced a legacy system of this magnitude on my own before. I appreciate any advice or feedback you guys can offer. Also let me know if there's anything else I should research.
Thanks
You can think of a configuration where you have separate logical/physical back-end servers for each system. Then you can have a front-end proxy (for instance Apache with mod_proxy) serving all the requests and separating them between the different back-ends.
This will also work as an application level "firewall" protecting you from unwanted requests, since you will only forward URLs that you recognize.
With regards to #1:
Big picture, while it's tough to say with the level of detail you've specified I'd say you'll probably want to make the system homogenous: use one technology and permanently redirect the legacy pages. It'll be much more cost-effective to maintain. Port the legacy WordPress content over to a new, single system.
With regards to #2:
If you're using ASP.NET, you can write an implementation if IHttpHandler to do the URL redirection, issuing an HTTP 301 (permanently moved) so that Google knows where the content has been moved to. I'd imagine other technologies have similar capabilities.
With regards to #3:
If you're using a single technology, this issue should be alleviated.