We have a running multi-lingual app hosted in Azure written in AngularJS. For managing some of the unsecured/public pages, we are looking for hosting another app with a CMS. So our app structure is would look something like:
App: www.example.com
CMS: www.examplecms.com
What we want to achieve is that dynamic content generated by CMS (different domain) for static pages be served using urls in www.example.com. Is it possible? We are primary targeting .net based CMS solutions but are open to other platforms. The static content is not too complicated.
Since the app supports multiple languages and most of the CMS solutions available offer multi-language support via subdomain.example.com or www.example.com/language/ directory structure, we want the custom url redirection to point to our app site (www.example.com).
Looking for suggestions you opinions or best strategies to work around this problem.
This Q is off topic, nether the less...
As you would essentially be running 2 entirely different web sites, yes everything would work just fine. The requirements are vague and very generic but any application/CMS could be setup in different domains and if you wanted requests made between them, allowing cross origin requests would allow sharing content/data.
Umbraco, like many CMS's supports multilingual sites using path prefixes as you mention along with any other method you are willing to write yourself.
Related
Here is a question on how to structure a web app based on react.
We are planning on deploying the front-end of an app that will contain several parts like main part, a customer account part and say a backoffice part for the company staff to track customer's data etc...
The plan is to deploy this app on Netlify and use subdomains like example.com, backoffice.example.com and clients.example.com.
My question is: shall we use a single React app to handle these 3 parts or use 3 different React apps ?
Initially we thought using 3 different apps would be better in terms of maintenance and evolution but any professional feedback with pros and cons would be appreciated.
Thx a lot.
We do something similar (but with Angular). It works well as each of the teams is responsible for their own app as far as maintenance and release cycles is concerned. It is pretty scalable as well - no problems to just keep adding new apps (as we are doing).
We have the whole lot behind NGINX, and so in the code we can just refer to simple paths like /client-services, /marketing and /sales - i.e. no server/protocol configurations.
You need to keep the following in mind :
How the apps interact with each other i.e. a standard data object, or cookies/localStorage
Authentication
You will be using app/internal routing for modules within your app, and external routing to redirect to other apps
We've been burnt before with one monolithic app...
I have a simple react app with a firebase backend. My app lets people create profile pages. I want to let people point their domain to their profile page. I don't even know where to start or what to search for. How would one let users point their custom domain to a specific route in a client-side react app?
There's a lot involved here, so I'm just going explain a very first basic step here.
One of the first things is that you'll need to be able to point multiple domains to the same back-end code, and then service different content based on the incoming domain. So that www.joshpittman.mytld will serve different content than www.frankvanpuffelen.mytld. This typically requires that you can programmatically map new domains to the existing backend code, which then serves different content based on the requested domain.
Firebase Hosting does allow you to mapping multiple domains to a single project, but there is no API to add new domains. You'd have to manually add each user's domain in the Firebase console, which seems unfeasible at any reasonable scale.
So if you want to implement this functionality, you might want to consider other options for hosting, specifically ones that have an API to add domain mappings, or that allow wildcard mappings. Since recommending specific ones is off topic on Stack Overflow, I recommend you do some searches with those specific terms to find good options.
Let's suppose an application written in Cake2. This application is huge. This application is mainly about CRUD's. Rewriting this application into Cake3 could be very time-consuming.
Now, I need o extend this application with lots of functionality. More and more CRUD's.
Application interface must look same, there must be single authorization and authentication provided by old app, or maybe rewritten into new app.
Now, is there any way, that existing application ( in Cake2 ) could work on same domain with Cake3?
I know that added functionality could work on subdomain like
Cake2 app is domain.tld
Cake3 app is storage.domain.tld
but how complicated, problematic could be set things as
domain.tld/[beefs|chips|sausages] <- Cake2
domain.tld/storage <- Cake3
Opinions?
It's pretty easy. Just configure your webserver to route /storage to your Cake3 app and all other to the Cake2 app.
Configure nginx with multiple locations with different root folders on subdomain (concept is the same)
https://www.nginx.com/blog/creating-nginx-rewrite-rules/
Google knows a lot more :)
I want to create a limited version of my app on mobile.
My app is at www.accountingguru.in (appid: accountingguru-india.appspot.com). It is using Servlets/GWT/Objectify 3.1
I am figuring out how to move forward with the design/development choices for a limited mobile app
What is a good url for Mobile User experience.
www.accountingguru.in/mobile
mobile.acccountingguru.in
-Aswath
It can be both if you properly set your domain names (and GAE mapping) and use some url rewriting. The first option might be easier from the authentication perspective.
If you use GWT/GAE it needs to be a common project if you want to have one GAE instance. In practical terms you can not have two different GWT projects and upload them to same GAE instance. As far as GWT goes - you can have two separate entry points: one for desktop and the other for mobile browsers.
You can have same url.
Use deferred binding to achieve different UI according to user.agent
Define a module .gwt.xml to detect the user.agent
On your applications's module use the return value to choose the appropriate implementation.
Have a look at the sample projects in gwt.
It seems like static files can only be served from the same domain as the app.
I could create a new app for hosting static files but I'm a little nervous that that would a violation of the terms of service.
You don't need to serve your static content from a different app, you just need to use a different hostname. App Engine makes it pretty easy to have many different hostnames that point to the same app.
With wildcard subdomains you don't even have to create a DNS entry. If your app lives at myapp.appspot.com, you can also reach it through any subdomain, like static.myapp.appspot.com. If you're using your own domain, you'll need to configure it manually.
"4.4. You may not develop multiple Applications to simulate or act as a single Application or otherwise access the Service in a manner intended to avoid incurring fees"
"You may not develop" but, you can "Enable Billing" for multiple application. An example:
1) mysite.appspot.com
2) mysite-static.appspot.com
3) mysite-data-service.appspot.com
Section 4.4 of the terms of service prohibit one from splitting one logical app into two pieces - so hosting your dynamic content and static content in two separate GAE apps would violate the terms.
However, you could host static files on another web hosting service - anything from a simple shared hosting solution all the way up to a big CDN. This approach enables your site to serve static content from domains other than your app's domain.