my_site | My personal website , simple blog , in python using Flask | Static Site Generator library

I downloaded the Enterprise Site Manager v2 and created the XML through the tool and it works, for whatever reason. Before I copied and pasted into notepad and plugged in my sites. I am going to mess with this, maybe try the manual XML again with the info from v2, see if that takes. i am also going to run the clear cache as I need to add and remove sites while I test.

Finally I got the answer from a facebook group. Thanks Hassan Aly Selim. Since, my Nginx server and my Django website are running on the same machine, server_name should be localhost (Nginx will access website within the same network). For more understandability, I'm putting the modified configuration below. my_site.conf

My doubt is: should routing be handled by Django or should it be handled by Vue in a SPA?

Your FE needs to know the routes if you're going to do SPA, e.g. your FE needs to know how to update the URL if user clicks on a link/item. Otherwise there would be page refreshes or wrong URLs.

So here i'm not using Vue to handle routes, but i load individual Vue components of the same app in those Django templates where i need them. My doubt: is it a bad practice? Are there reasons for which i should avoid doing so?

I think you need to decide it you're going to build a SPA or not. My rule-of-thumb is SPA is better if have a lot of interactions on your page or you have a team of speciallized people for FE. Having a total separation between BE/FE is definitely industry de-facto standard but rendering most stuff on BE and having a lightweight FE is not a crime either, Stack overflow itself uses such approach.

If you're going with SPA, putting FE URLs in BE also makes not much sense (unless you're doing something like server side rendering). BE will provide a set of API URLs (invisible to end user) and FE will consume them and provide a set of FE URLs that users would see.

Yes, the main problem is that having the apps hosted on two different domains might make me lose a lot of django benefits in terms of security. I have some doubts on storing a jwt token on local storage, i don't think its the safest solution; there is session based auth but i don't know how would it work on two different domains. Another thing is the lack of examples on this, and finally the biggest problem is that i already setup the app on this environment, so moving to decoupled would be quite a pivot

There are multiple answers for your concern.

1- There's no need to have separated domain. You can prefix all your BE URLs with /api/ then on production you can use a reverse-proxy like NGINX or Traefik or your load balancer, ... to separate the two. Having separate domains is easier to maintain in long run but you'll need to handle cookie/CORS issues now and then.

2- If you have separated domains you can set cookies on the main domain from subdomain with this settings

3- There's no need to go with JWT token in localstorage. IMO it's inferior to having httponly cookies. Django session auth has httponly turned on by default. This way random npm libraries you installed or 3rd party scripts on your page has no way to access and steal the token.

4- On a separate note, Django CSRF protection is kinda obsolete now we have samesite cookie on browsers. Check browser support here. Newer versions of Django defaults to Lax that protects you from CSRF on supported browsers. So you can turn that protection off to have one less headache.

I personally think you can stick to Django session based auth, no need to add anything to your FE. FE will just call /api/auth/login and proper cookies will be set automatically.

To be more robust you can add an API like /api/auth/me that returns current logged in user data to FE. FE will call that when user visits your website for first time to understand if user is logged in or not.

You don't need to fix anything in index.php. Analytics counters can be added to the layout (~/themes/mytheme/layout/mylayout.htm) of the page between the

You should specify different namespaces, and app_name=… is not a valid parameter for include(…). You in fact do not need a namespace in the first place, you can in both urls.py specify an app_name:

For any field in TypoScript that uses the getText data type, you can use path: for that. For example:

The main issue is that you are using the literal string (single quotes) as the title to your file object instead of an interpolated string (double quotes). update your file object to the following an i think it should work

Maybe I didn't understand something but why don't you just run the code ran in your eventlistener's function in the main thread?

In the event where you work with dates later on, you could make a separate function for it, like so:

1. You can do a redirect from the subdomains to your page but in this case you will have the 3rd party URL displayed and not your subdomain.

2. You can probably use a simple HTML structure with iFrames to include your page. Like connecting your subdomains with a server and hosting there a HTML page which loads your python or WYSIWYG page.

3. If site123 is a static landing page without many changes or dynamic elements, I would think about scrapping it with a script and transfer it to a server which also supports python (e.g. Amazon AWS). In this case you can get rid of pythonanymwhere and use your subdomains. Then you can either use site123 (and scrape it every night for example) or use another WYSIWYG editor to build a page and deploy it to your server.