ecom | Ecommerce website with laravel Project Code | Learning library

A good practice is to use a configuration file that contains theses configuration properties (application.properties)

You can use a Docker file like this:

At least three reasons why you need to re-create it properly (2 technical and advice):

1. ExternalName is used for accessing external services or services in other namespaces. The way it works is when looking up the service's name happens, CNAME will be returned. So in other words it works for egress connections when requests should be directed somewhere else.

   See service - externalname type and use cases Kubernetes Tips - Part 1 blog post from Alen Komljen.

   Your use case is different. You want to get requests from outside the kubernetes cluster to exposed loadbalancer and then direct traffic from it to another service within the cluster. It's not possible by built-in kubernetes terms, because service can be either LoadBalancer or ExternalName. You can see in your last manifest there are two types which will not work at all. See service types.

2. Avoid unnecessary complexity. It will be hard to keep track of everything since there will be more and more services and other parts.

3. Based on documentation it's generally possible to have issues using ExternalName with some protocols:

   Warning: You may have trouble using ExternalName for some common protocols, including HTTP and HTTPS. If you use ExternalName then the hostname used by clients inside your cluster is different from the name that the ExternalName references.

   For protocols that use hostnames this difference may lead to errors or unexpected responses. HTTP requests will have a Host: header that the origin server does not recognize; TLS servers will not be able to provide a certificate matching the hostname that the client connected to.

   Reference - Warning

You should refer to the nested properties of the address and shipping_address objects in your schema when registering a new user:

The product_type object in your schema indicates that every object inside it must have a color key-value pair. The error was about your second object in product_type (index 1) does not have the color key. You should change product_type from an array to an object. I.E.

The definition of a headless service is to not provide a DNS record and provide internal load balancing.

A headless service can be used to query the endpoints and handle them separately.

To fix your issue create a regular service.

You claim "it was working fine before". What happened in the meantime?

What you can do as checks is to find out if a process is listening to port 3306:

I feel like this is pretty "hacky". Are there any security issues involved with what I've done here?

A GET request is not supposed to have side-effects. Indeed, as the HTTP specifications say [w3.org]:

In particular, the convention has been established that the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered “safe”.

You should make use of POST, PUT, PATCH or DELETE to make requests with side effects.

Django will automatically try to validate a CSRF token if you make a POST request. This to prevent a vulnerability that could result in a malicious JavaScript file that uses the credentials of the logged in user to make requests. Django (aims to) prevent this by using a CSRF token. You add such token to the POST request as is explained in the AJAX section of the documentation:

According to the docs the estimated maximum throughput is 4000 rps. If you have 8 scale units the estimated maximum throughput is

32.000 rps
1.9m rpm
115.2 rph

You can have up to 12 scale units so you should be safe to handle such a load. (You can call to have > 12 scale units if needed)

XPath is a selection language: it can only retrieve nodes that are actually there, it can't change them in any way. If the selected element has a prefix and namespace in the original, then it will have a prefix and namespace in the result.

However, you need to distinguish what the XPath selects (a node) from the way it the result is displayed. This depends on the application that is evaluating the XPath. The two popular ways of displaying a node selected by an XPath expression are (a) by serialising the node as XML (which is what we see in your case), and (b) by showing a path to the selected node, such as /d/m:properties/d:TextLine. You haven't told us how you are evaluating the XPath expression or displaying its result, and you may have options here.

But perhaps you should consider XSLT or XQuery, which (unlike XPath) allow you to construct new XML that differs from your original.