captain

In order to make a call to the PHP file after a successful payment, you could easily do a call to the file using jQuery's .post() method.

Below is an example of what the post call would look in your JavaScript code. Using this will successfully call your PHP file once the JavaScript is invoked and you can use the data payload to return the data from the PHP file back to the original page.

The Total field must be at the level of ReservationVM (unless you want a vessel named Total, which you don't). Also, you should create another class, let's call it VesselReservationVm. You can do something as follows:

Classes:

Following my comment above

You might have an easier time of it if you split into lines first, and then split into words, because I expect the abbreviated character names will always be at the start of a line? Also, I notice the line is indented a couple spaces when a new character starts speaking. That could be another thing to look for.

Split into lines:

The issue is on your query

If isSenior is defined in Member, you just need to restrict T to Member or its subtypes:

Use res.json() to get json data from api.

Use one of these, I’ve seen guys break into accounts that were missing 8 words with the solver-server.

BIP39-Solver-CPU: This is the CPU benchmark tool he wrote in Rust to get an idea of how long it will take do solve on a CPU for certain number of unknown words.

https://github.com/johncantrell97/bip39-solver-cpu

BIP39-Solver-GPU: This is the actual GPU version he ran on each worker GPU to solve this problem.

https://github.com/johncantrell97/bip39-solver-gpu

BIP39-Solver-Server: This is the actual server he ran that handled distributing the work to all the workers.

https://github.com/johncantrell97/bip39-solver-server

You defined the postgres superuser as POSTGRES_USER: my_app (see the readme on dockerhub for details), but try to login with username postgres (psql -U **postgres**), which doese not exist. If we switch it to my_app, it should work. Same goes for the health check.

Alternatively, we could set the POSTGRES_USER to, e.g., postgres or root (or whatever we want) and provide initialization scripts to the container's directory /docker-entrypoint-initdb.d/. All *.sql-scripts in this folder will be executed on database startup. A common approach is to mount a host-directory, containing all scripts (e.g. creation of a new role, creation of a new database, and giving the new role ownership to this database) to this container-directory. An example can be found in this bitbucket repository of mine. We can just focus on the postgres container and the postgres directory, since those are the important parts.