My question is can I just type http://mydomain.com (without port address and MyWeb) to show my web site ?
Is this handle via ABM or via domain or what? I am newbie to this kind.
Without port address = port 80 for http, or port 443 for https.
If these ports are not already open then you can configure your ABM server to listen on these ports.
In most cases you will need to configure a backward proxy. @alwaysbusy probably has more experience with the required configuration.
Note that you need to run a backward proxy that supports WebSockets.
My question is can I just type http://mydomain.com (without port address and MyWeb) to show my web site ?
Is this handle via ABM or via domain or what? I am newbie to this kind.
Without port address = port 80 for http, or port 443 for https.
If these ports are not already open then you can configure your ABM server to listen on these ports.
In most cases you will need to configure a backward proxy. @alwaysbusy probably has more experience with the required configuration.
Note that you need to run a backward proxy that supports WebSockets.
I don´t think the www folder is the correct place for it.
You need to put the file to a server path accessible to your webserver listenening at port 80.
It is the Apache (?) task (http daemon) who is reading and handling .thaccess files.
I don´t think the www folder is the correct place for it.
You need to put the file to a server path accessible to your webserver listenening at port 80.
It is the Apache (?) task (http daemon) who is reading and handling .thaccess files.
To be honest, we outsourced that part ourselves. I know there is an Apache and HAProxy running on the server but how it is configured exactly, no idea.
I did not know one could use the .htaccess file to do that too. It should be placed indeed in your Apache (port 80/443) www, NOT in the ABM (port e.g. 51042) www! The ABM app should be placed in your HOME folder, NOT the Apache www folder.
Possibly more importantly what OS will you be using when you deploy for real?
.htaccess sits just above your www folder and is often hidden from view.
If you're currently on a Windows box and will be eventually deploy to a Linux machine then I'd simply not yet worry about getting it to work as you want right now. You can sort that when you deploy for real.
Hi all,
correct me if I am wrong (I didn't yet use ABM-wonder so far).
Turning off Apache (ISS or any other "standard" webserver) and setting ABM to ports 80/443, we would have a chain like the following:
DNS-->Static IP of server machine --> ABM
since ABM would be the only service listening on ports 80/443, right?
It could be used to show a minimalist website too if a few static html pages are stored in its www dir, right?
Possibly more importantly what OS will you be using when you deploy for real?
.htaccess sits just above your www folder and is often hidden from view.
If you're currently on a Windows box and will be eventually deploy to a Linux machine then I'd simply not yet worry about getting it to work as you want right now. You can sort that when you deploy for real.
But you want to start the app with pointing to a port 80 url.
So you need to extend the port 80 webserver functionality to forward requests to the b4j app runing on another port. THIS is what the .htaccess does/supposed to.
To be honest, we outsourced that part ourselves. I know there is an Apache and HAProxy running on the server but how it is configured exactly, no idea.
I did not know one could use the .htaccess file to do that too. It should be placed indeed in your Apache (port 80/443) www, NOT in the ABM (port e.g. 51042) www! The ABM app should be placed in your HOME folder, NOT the Apache www folder.