Is there a way to get coffee script source maps when deploying to meteor.com or Heroku?
You could deploy with --debug to meteor deploy hosting. I'm not sure about deploying to Heroku since you would be using a bundle (if you use the meteorite buildpack).
Related
deployed Lumen micro services using azure devops and suddenly it started giving 500 internal server error after successful deployment.
Set the same package version on deploying to Azure App Service as the package version that worked locally, for local environment.
App Service runs your app in production mode, so you need to make sure that your project works as expected in production mode locally. Depending on your composer.json, different packages may be installed for production mode (require vs. require-dev).
Thanks, for the answers but I got it fixed by adding flag --ignore-platform-reqs to composer install in yml file.
I`m looking for a hosting package for scala and play in Amazon elastic servers. If there is anybody here is done it before? what are the ideal solution for a small ERP application?
you can easily deploy playframework web application on elastic beanstalk using docker container.
Create environment on EBS using docker container.
package your app using sbt docker:stage
make a zip of target/docker/stage/*
deploy this zip on EBS environment.
you can explore docker # https://www.docker.com/
Over the last few months I've become familiar with the AWS OpsWorks deployment process as it pertain to Node.js - deployment for Go seems to be another animal.
From what I've gathered, this is what I need to compile a successful Go deployment:
Install go on the EC2 box
Pull the private repository from GitHub
Pull in all dependencies
Compile the main package for the box's arch
Start the binary with a couple of flags that I use
Everywhere I have read seems to tout the ease of Go deployments because dependencies are included in the binary, but that seems to imply that you are compiling the application in your development environment and pushing that up to the cloud. This doesn't seem like a process that works well across a development team.
https://github.com/crowdmob/chef-golang-web-server-cookbook
I have been attempting to get the Chef Scripts from CrowdMob working, but to no avail. I continue to get errors that look like this:
[2014-08-01T16:08:22+00:00] WARN: Cookbook 'templates' is empty or entirely chefignored at /opt/aws/opsworks/current/merged-cookbooks/templates
What is the proper way to deal with dependencies during deployment?
Are there any established practices for deploying Go onto AWS with Chef?
Use a continuous integration service like CircleCi, Travis or your own setup Jenkins.
On the Continuous integration service then
Add a github post commit hook .
Test / Build the binary
Create the zip file as artifact
At this point you can create an new version on Elastic Beanstalk using the AWS commandline and the zip file created from this version.
venv/bin/aws elasticbeanstalk create-application-version ...
Then just select which version to deploy from the EB dashboard.
For simple services using Chef is overkill IMHO. Docker offers a simple workflow.
Use the Docker container option and then use elastic beanstalk's command-line client to initialize your environment in the project root directory and then you can simply do a 'git aws.push' from the same place.
With the correctly configured Dockerfile in your project and pushed to eb, the EBS' docker container app will pull the correct image with golang installed, then do a go get on your projects dependencies, and then compile and run your app. It sounds way more complicated but it's actually very easy.
Below is a link to a video walkthrough I did for running a simple golang webapp on EBS. The method for uploading the project does not use git. Instead, I zip it up and upload it, but the git method is recommended (and I do it) for automating deployment.
YouTube: How to run a go web app on Amazon's Elastic Beanstalk
I also had some problems to setup a good building process with Elastic Beanstalk and Go.. I don't want to use Docker, and all the people seems to be going on this direction.. so.. you can take a look at this project: https://github.com/battle-arena/heimdall
There you will find a custom setup using the Buildfile and the Procfile.. and I rely on a CI system to build the release package...
Basically I do the following:
Hook the commits to a CI system
On the CI system I run the test and the install.sh if all good
The install.sh will create a build folder and a structure that will be sended to the Elastic Beanstalk with the aws-cli tool
After send to the EB the Buildfile will run the build.sh that will basically extract the compressed package with the proper structure, and run a go get ./... and go build
The Procfile will run the generated binary
I think the result is pretty good, and you can use with any CI tool.
I'm checking out my options on deploying meteor apps.
I already saw the problems of deploying meteor apps built on my mac, to remote Ubuntu server and other versioning issues, i believe more to come.
meteor-up looks like a good solution, but can it be used alongside with demeteorizer
to handle dependency management?
Would that have any advantage over packaging with demeteorizing, and deploying with some othe/custom script?
You don't have to use demeteorizer, if you're using mup. You can configure npm binary dependencies in the config.
Personally I use mup in production, for over 10 different apps, and it even handles multi-node deploys nicely.
I recommend using something like chef to setup your environments, and then mup for meteor/node/mongo/phantom.
I am trying to create and deploy a grails application on the cloud bees i tried using both, cloud-bees sdk and as well as the eclipse sdk . I don't no much how to use the cloud bees sdk so I tried using the eclipse sdk.
In eclipse SDK the command is being executed but only thing fails is that it throws an error, now I want to create and deploy the application on the cloud.
Can you please help me?
You should use the CloudBees SDK to deploy a Grails application on CloudBees platform.
You can find the documentation here.
Basically, you can see on the doc these are the steps in the case you don't need database binding:
Create your application
bees app:create -a my-app jvmPermSize=128
Setting the Grails Environment of the Tomcat server
bees config:set -a my-app -P grails.env=production
Deploy your application
bees app:deploy -a my-app target/my-app-0.1.war
You can generate the war file of your application using the command below:
grails war