A client told me to deploy a docker image for him on Cloud Run. I am able to do that in my own account. Once it is done, the problem is that it is to me to pay the maintenance fee. Do you know the best practice to avoid this problem ?
Should I tax my client every month ? Or should I deploy the docker image on the gcp account of my client ? Or is it possible to directly tax my client from my gcp account ?
Thanks in advance and sorry for this silly question.
Best regards.
You only have two choices:
deploy in your project and pay the fees. How you manage reibursement is up to you.
deploy in your customer's project and they pay the fees.
Best practice: deploy in their project so that they own the service and are responsible for that service, e.g. following Google Terms of Service.
Related
I'm fairly new to Akka.net and I'm a total noob when it comes to containers so please forgive me if this is too simple (but I kind of hope it is).
I'm trying to build a web app cluster using Azure app services. I want the lighthouse to be hosted in an Azure container instance. I've been successful putting the cluster together on my local box (without docker). I've tried standing up a local docker container with port forwarding but I haven't been able to get it to work.
Thanks in advance for your help.
You can definitely do this, but since you're using Azure App Services I'd recommend taking a look at Akka.Management and Akka.Disovery.Azure instead.
This will eliminate the need to use Lighthouse at all - and instead your nodes can form a cluster on Azure App Service by querying a shared Azure Table Storage table instead.
There's a complete Azure App Services demo that shows how to do this here: https://github.com/petabridge/azure-app-service-akkadotnet
And the relevant code is here: https://github.com/petabridge/azure-app-service-akkadotnet/blob/dev/src/Akka.ShoppingCart/Startup.cs
NOTE: this uses the Akka.Hosting methods, which eliminates 99% of HOCON configuration and ties into Microsoft.Extensions for configuration, hosting, and DI. Akka.Hosting is a relatively new package and just hit stable at the end of 2022. You should definitely use it - all of the documentation and examples will be reworked to incorporate it once Akka.NET v1.5 ships at the end of February, 2023.
Is this correct that Jira is installed on one's server or local computer and that's the only way to run it?
If not, how can I run, or connect to, Jira on Atlassian's server?
Namely, at this point I don't want to install anything on my VPS or computer, and instead I want to be able to run Jira in the cloud, the same way I'd sigu up for and then use bitbucket or github. That is, by creating an account. I need Jira for a couple of days only, to test some REST API.
Where does one sign up for Jira? There's no way, is there?
At the current time Atlassian provides a free plan for its Jira cloud service.
See here: https://www.atlassian.com/software/jira/pricing
I've been developing a web application for a very amazing charity for the past two months. I have a Docker image, container, repository etc. and want to publish my web app for the public to see and interact with. It is a UK/Ireland based charity.
The problem is that hosting seems to be quite expensive. Is there any discounted/free hosting services available for non-profits to host their applications? I've seen some for US Charities. Are there any services providing a discount which would be able to host my Docker container? Right now it is sitting on the free version of Heroku, which is definitely not suitable for a lot of traffic.
(Also, I'm new to hosting/Docker so any tips/first steps would be well appreciated!)
Azure has an excellent grant plan for verified NPOs you can use for anything (we are using it).
Azure isn't the most user-friendly, but it's probably worth the effort to get to know it.
Amazon Web Services provides a grant of $1000 per year, but you have to pay a $95 admin fee.
AWS, through TechSoup, will make one grant of $1,000 in credits per fiscal year (July 1 to June 30) to eligible 501(c)(3) organizations. Organizations can apply these service credits toward usage fees for all AWS on-demand cloud services, as available by region. AWS credits are not valid for Amazon EC2 Reserved Instances, Amazon Mechanical Turk, AWS Marketplace, Amazon Route53 domain name registration or transfer, or any upfront fee for any service. They are available for monthly support fees.
I was looking around for some time, but couldn' t find a free add-on to manage test cases, test plans et scenarios ect.
Do you know any who is free that can be installed on a Jira cloud solution ? or should i create my own custom Jira project for it, if there is no free one
Thanks
You could try the TestFLO app - it's available for both Server and Cloud instances of Jira. Not fully free, but at least you've got a free trial :) You can find it on Atlassian Marketplace, just like any app for Jira.
I have just deployed my Grails app on public cloudfoundry(myApp.cloudfoundry.me) and i need my domain to point to it. How is this accomplished? or what are the alternatives?
Problem: deploy Grails app via cloudfoundry on cloud with my own domain name instead something.cloudfoundry.me
Resources: i have a virtual server Ubuntu with static public IP available.
Goal: have a way to deploy many of my apps each with their own domain names
If you don't mind sharing how you do it today and, perhaps, if you can reference tutorial that would be very helpful
Thank You,
Cloud Foundry does not currently support custom domain mapping. However, this feature is high on the priority list and development is currently under way. If you do a search at Cloud Foundry Support
you will find a series of posting regarding this issue and some short term workarounds that could be helpful for you and your particular situation.
Thank you eightyoctan! I accepted your replay as answer, however. i wanted share what i end up doing to have my domain point to cloud foundry hosted app
Option 1. i used GoDaddies Forward+Masking to push app on myapp.cloudfoundry.com and then forward+masking on godaddy to have mydomain.com point my app on cloudfoundry....i am sure i am penalized from SEO aspect to some extent but it works so far
Option 2. I also believe the same goal - have my custom domain point to cloud foundry app via Elastic Ip of EC2 as described in the following blog:
http://www.cloudsoftcorp.com/blog/first-steps-with-cloud-foundry-on-amazon-ec2/
Or use Stakato with EC2 that runs on top of cloud foundry from what i can tell. For more:
http://docs.stackato.com/server/ec2.html#vm-ec2
Either way, I hope cloud foundry does get this feature soon so we don't have to make extra steps to accomplish this