Im trying to build server for my project where frontend is react and backend is django. I did it locally works just fine, but how I should deploy it on google cloud platform, i want to make it live through external ip of my virtual machine. I tried everything what i found on google, but usually all guides are for localhost.
You could follow this link, it's a tutorial to learn how to deploy an app in a compute engine with django, also this video could help you.
With this link you could learn how to add the firewall rules in case you require to open a specific port.
Just in case I leave you this link, where you can learn how to deploy a django project in Google Cloud Platform with it's different products.
I hope this information is useful for you
Related
I am trying to host my Autodesk Forge model on AWS, in the process of creating the stack, there is this error (https://aws-quickstart.s3.amazonaws.com/quickstart-autodesk-forge/templates/autodesk-forge-master.json)
I just found this error shows that the file does not exist.
How can I solve this problem?
How can I find this file (autodesk-forge-master.json)?
The Learn Forge website has a Deployment section that provides tips for deploying your application to various cloud hosting providers, incl. AWS, Azure, or Heroku.
However, if you're getting started with Forge (now called Autodesk Platform Services) development, I would suggest using one of the PaaS solutions such as Heroku or Fly.io.
Learning AWS and looking for guidance on how to best put this app onto the web.
I have a fairly straightforward app:
Frontend build in Vue
Backend built in Laravel
In hindsight, I wish I'd just used Inertia within the Laravel app but alas.
Authentication is via JWT and users are stored within the backends connected database.
What I've already tried:
Attempt One
Using Elastic Beanstalk for Laravel hosting
Amplify for the frontend hosting
The issue I faced was EB uses http where as Amplify uses https so I couldn't get the two parts to talk to each other.
I then tried to use Router53 to make the connection (by buying a domain) but couldn't get the connection to work.
Attempt Two
I tried to put everything on an EC2 instance. Unfortunately, that was way too involved and my skillset isn't yet strong enough to progress there. I don't even know if it's even possible.
Conclusion
Anyone can provide direction on how to best host this app? Its just a practice app and I'm just learning.
Thank you for your help!!
I can't find any proper guideline how to deploy a Django web application on Windows Server, almost all tutorials talk about Linux. Can someone explain or give a link?
I now we need an IIS. What about DNS and AD, or any other services? I would like to know the relationship among IIS, DNS and AD, or any other services.
One simple way to deploy a Python app to Windows app service is to use the Devops Projects
Step 1: Create a Python Project
Step 2: Choose an application framework as Django
Step 3: Select the Windows Web App
Step 4: Fill the rest of the settings.
Once the project is created you can pass the custom code and do the deployment from the Azure Devops pipelines.
EDIT
if you want to deploy the app on VM follow the steps as mentioned here.
I am very new to GCP and G-Suite. I wanted to understand one basic thing:
If I create an application (to be used within a domain) using App Maker, do I also need access to GCP?
I have done lots of googling [https://support.google.com/a/answer/9142070?hl=en] but couldn't find answer to this.While watching to one video on AppMaker I realised that- I can create application which could interact with G-Suite apps but we can not preview/publish this application without having account/access to GCP as "previewing" an app actually deploys the app on App Engine which is part of GCP. Also "publish" would definitely be doing the same.
Can any one help me in understanding this? I want to start my page development in App Maker and want to spend money on GCP later, this is doable only when preview is not dependent on GCP?
Any quick reference would be appreciated.
Regards.
App Maker is dependant on GCP products: Google Cloud SQL and Google App Engine; Although, the latter one is not being charged. This information is located in the official documentation.
App Maker apps usually store data in Cloud SQL, a Google Cloud Platform (GCP) service that delivers fully managed SQL databases in the cloud.
I configured a parse server on my AWS elastic beanstalk using this guid I've tested it and it all works fine
Now I can't find a way to deploy parse dashboard on my server.
I did deployed parse dashboard on my local host and connected it to the application on server, But this way I cannot manage (Add and remove) my apps.
Another problem is that parse dashboard missing cloud code on default, I found this on git, but I cant understand where do I add the requested endpoints, is it something like adding app.use('/scripts', express.static(path.join(__dirname, '/scripts'))); on the index.js file?
in order to deploy parse-dashboard to your EC2 you need to follow the Deploying Parse Dashboard section in parse-dashboard github page
parse-dashbard github page
Please make sure that when you deploy parse-dashboard you are using https and also basic authentication (it is also part of the guide)
Now regarding the cloud code: the ability to deploy cloud code via parse CLI and to view the nodejs code in parse dashboard are not available in parse-server but those are parse.com features. Cloud code in parse-server is handled by modifying the main.js file which exist under the cloud folder and deployment should be done manually by you but the big advantage in parse-server cloud code is that you can use any NodeJS module that you want from there and you are not restricted to the modules that were used by parse.com .
Another point about the dashboard. What you can do is to create an express application and then add parse-server and parse-dashboard as a middleware to your express application and deploy the whole application to AWS and then you can enjoy both parse-server (that will be available under the /parse path, unless you changed it to something else) and parse dashboard that will be available under the /dashboard path
Enjoy :)