You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, this is really wonderful project that taught me a lot. However, I found myself completely lost on the hosting part, and now I am stuck with a customized application inspired by your app that is working on localhost well, however I am unable to make the authentication work outside the localhost.
If I am correct, when using the Sanctum's cookie based authentication, the Vue front-end and Laravel back-end needs to be hosted on the same domain in order to avoid cross-origin errors (like in your project). So, when I try to deploy the front-end to Netlify and Laravel on a separate domain on Heroku, the cross-origin policy fails (which makes sense). I was glad that you provided some information about the hosting, so I tried to use Netlify like you presented in the documentation, but I find the lack of information in your documentation to be overkill for me.
It probably comes from the fact, I don't understand how to handle the domains and their SSL encryption right. I purchased domain through Cloudflare, but I am unable to encrypt it in the Forge and when I tried transformed the domain through Netlify, so then both back-end and front-end fails to load. When I tried to encrypt the domain right away before changing the nameservers to Netlify name servers, it worked well.
I will probably try to purchase VPS instead and use Nginx to try to deploy it.
But is there any chance you can extend the documentation? I think this may be the crucial and most vulnerable part for any solo full-stack developers trying to deploy the app, since we are usually more of the programmers, but less of the DevOps guys.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, this is really wonderful project that taught me a lot. However, I found myself completely lost on the hosting part, and now I am stuck with a customized application inspired by your app that is working on localhost well, however I am unable to make the authentication work outside the localhost.
If I am correct, when using the Sanctum's cookie based authentication, the Vue front-end and Laravel back-end needs to be hosted on the same domain in order to avoid cross-origin errors (like in your project). So, when I try to deploy the front-end to Netlify and Laravel on a separate domain on Heroku, the cross-origin policy fails (which makes sense). I was glad that you provided some information about the hosting, so I tried to use Netlify like you presented in the documentation, but I find the lack of information in your documentation to be overkill for me.
It probably comes from the fact, I don't understand how to handle the domains and their SSL encryption right. I purchased domain through Cloudflare, but I am unable to encrypt it in the Forge and when I tried transformed the domain through Netlify, so then both back-end and front-end fails to load. When I tried to encrypt the domain right away before changing the nameservers to Netlify name servers, it worked well.
I will probably try to purchase VPS instead and use Nginx to try to deploy it.
But is there any chance you can extend the documentation? I think this may be the crucial and most vulnerable part for any solo full-stack developers trying to deploy the app, since we are usually more of the programmers, but less of the DevOps guys.
Beta Was this translation helpful? Give feedback.
All reactions