I created a simple Vue.js application. I am trying to deploy it on Google compute engine(not app engine or any other), but I can't find any appropriate solution. Can anyone help me?
Have a look at App Engine. It'll be the easiest way to deploy your app without thinking about infrastructure management.
If you really want/need to use Compute Engine you should decide on your own which OS to use and then install and configure all the required software manually.
Meanwhile, I should mention Cloud Run as managed compute platform that automatically scales your stateless containers with your code.
Please update your question if you need more details.
Deployed using express server, Nginx and pm2.
Related
How should i deploy new versions of molecular services?
The documentation explains well how to start them with moleculer-runner, but i can't find what is the proper way reload them without downtime.
The zero-downtime updating is not part of the framework, it's a system admin/devops issue. I recommend using Kubernetes for deploying upgraded containers with zero-downtime: https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/
I I just started using Google Colab for a project of mine. I see an button of "CONNECT" on the web page that presents before me two options:
Connect to Hosted Runtime
Connect to Local Runtime
Can anyone explain what the two mean and how it may affect my project? I did not find any useful documentation related to it.
Hosted Runtime runs on a new machine instance in Google Cloud. You don't need to set-up any hardware. But you may need to install a few libraries every time you use it.
Local Runtime runs on your machine at home. You need to install Python, Jupyter, and set-up some forwarding. It is useful if you have a lot of data to process locally, or if you have your own powerful GPU to use.
In most cases, I use Hosted Runtime.
I have a legacy VB.NET application that I would like to virtualize so my clients can access it from the cloud. Currently, I have an Azure VM that hosts the app and exposes it to the customers via RDS. Everything is working fine, but I am not 100% happy with the performance.
I would love to be able to convert it into a web application, but unfortunately this is not feasible at the moment.
I was wondering if there is a better way of doing this or perhaps there is a better platform that I could use.
Thank you.
Possible ways to accomplish it:
Creating dedicated WCF service for this purpose (currently my favorite option)
Using the REST API?
Azure PowerShell?
Explanation:
Publishing a web-role cloud-service takes about 10 minutes. It's much too long during development - I try to do as much as I can offline, unit-test-ish and modular, but it's just impossible to completely avoid development cycles altogether with the VM.
Apparently, the long time is mostly a result of the machine being wholly restarted, so I'm trying to find an automatic solution, like uploading and installing the binaries.
What is the best way to accomplish it?
What do you think? would it cut at least 50% of the publishing time?
Do you expect any critical problems?
The solutions proposed below are definitely against best practices and should NEVER-EVER be used in production environment.
If your objective is to quickly test your changes in your development environment, there are two ways you can go about it.
Enable RDP and copy your modified binaries or other files directly in the appropriate folders on the VM. You could enable Remote Desktop on your web role and copy the files manually in appropriate folders.
Use Web Deploy: This will only work for web roles in your project but you could enable Web Deploy on your Web Roles and use that to make faster deployment. Please see this link for more details on how to use this feature: https://msdn.microsoft.com/en-us/library/azure/ff683672.aspx.
I'm trying to build a small webapp that will handle our development environments located on an openstack infrastructure (version 2012.2.2-dev, bundled in ubuntu 12.04) and I need to create some volumes using the API (i decided to use openstack rest api). I'm able to start machines and do some other operations (everything is built based on this: http://api.openstack.org/api-ref.html). If I send the request to create a volume as explained on the api reference, i get a 404. I tried different api versions (v1), but still no success.
Thank you in advance.
What language are you coding in? You could just use an SDK for this and skip trying to talk to the API directly. See
https://wiki.openstack.org/wiki/SDKs
In newer releases of OpenStack it is preferable to make use of the Cinder API rather than Nova API.
In folsom, Cinder uses IDENTICAL API refs to Nova volume related API sets. This is because this was the first release to separate out volume management to cinder as a stand alone project. While volume API references remain in folsom it is not the default and it is not the preferred method for accessing volumes REST queries.
Check out.
http://docs.openstack.org/developer/cinder/