I would like to deploy Meteor version 0.7 and 0.8 up to CloudBees? what is the best way to do this and is this possible?
Yes this is possible.
This can be achieved using the "-t nodejs" command line option when deploying - as meteor can be deployed as a nodejs app.
The best way is to use "demeteorizer" to convert it to a plain nodejs app:
https://github.com/onmodulus/demeteorizer
Once you have the plain app - you can npm install and zip -r - the app directory - and deploy it normally on cloudbees as a nodejs app from there.
Related
I'm on the third module of this AWS tutorial to build a React app with AWS, Amplify and GraphQL but the build keeps breaking. When I ran amplify push --y the CLI generated ./src/aws-exports.js and added the same file to the .gitignore. So I'm not surprised the build is failing, since that file isn't included when I push my changes.
So I'm not sure what to do here. Considering it's automatically added to the .gitignore I'm hesitant to remove it.
Any suggestions?
I'm assuming you are trying to build your app in a CI/CD environment?
If that's the case then you need to build the backend part of your amplify app before you can build the frontend component.
For example, my app is building from the AWS amplify console and in my build settings I have
version: 0.1
backend:
phases:
build:
commands:
- '# Execute Amplify CLI with the helper script'
- amplifyPush --simple
frontend:
phases:
preBuild:
commands:
- yarn install --frozen-lockfile
build:
commands:
- yarn build
artifacts:
baseDirectory: build
files:
- "**/*"
cache:
paths:
- node_modules/**/*
Note that the backend is building first with the amplifyPush --simple command. This is what generates the aws-exports.js file.
The 'aws-exports.js' file gets created automatically when AWS Amplify runs the CI/CD deployment build process and gets configured with the appropriate settings for the environment you are deploying to.
And for this reason it is included in the .gitignore. You don't want your local test configuration to be used in your production deployment for example.
As per Matthe's answer above the should be generated when the build script runs the 'amplifyPush' command. For some reason this is not working for me at the moment though!
AWS added support to automatically generate the aws-exports.js at build time to avoid getting the error: https://docs.aws.amazon.com/amplify/latest/userguide/amplify-config-autogeneration.html
"meteor build" not working for me
http://screencast.com/t/iOjtsnA2l
I am on ubuntu 14 - Amazon Web Services (AWS)
And
I used these steps
https://rocket.chat/docs/developer-guides/pre-requisites/
Thanks for your help.
I believe I have found the issue, you need to specify an output directory. e.g. meteor build ../release would put the created tarball in the specified directory.
Can I Build a meteor android app in cloud 9.
meteor add-platform android
Because Im running on windows or should I install linux and run
curl https://install.meteor.com/ | sh
and build it locally.
If you want to build android app on Windows you need to be using the meteor 1.3 release beta which you can install by running meteor update --release 1.3-cordova-beta.5 in your project folder - Details on this release
Prior to 1.3 you will need to build the app on a linux machine
You can build a Meteor app on Cloud9 using any version of Meteor. See Meteor on Cloud9.
I am running a Dokku app in production and need to know what version of the app is running on the server.
Is this possible with Dokku?
There's no need for a plugin.
All apps in dokku are git bare repositories. Just connect to your server, switch to the app directory (mine are in /home/dokku/<app-name>) and run a git log. That should do the trick as well.
To get the current git commit hash for a dokku app just run
dokku config:get <myapp> GIT_REV
Yes, you can add the SHA1 of the latest git commit using this plugin: https://github.com/dokku-alt/dokku-alt/tree/master/plugins/dokku-git-rev
There are many other alternatives based on different scenarios and different environments. If you are deploying Node.JS apps and using package.json properly, you can easily parse out the version using the fs standard lib; JSON.parse(fs.readFileSync('package.json')).version
You can also do dokku config:show myapp | grep GIT_REV to get it from the app's environment variables. The above command assumes your app name is myapp.
The fastest way to do this is to issue this command:
dokku config:get GIT_REV
This queries the server for the git revision that was most recently deployed. During deployment the GIT hash is set as an envirnoment variable, that's why it's possible to get with config:get.
You can also just bash into your doku app and echo $GIT_REV
I've downloaded telescope from github and I'm trying to install it on my website.
unfortunately I don't know how? I tried it on my mac with no problems
git clone git#github.com:TelescopeJS/Telescope.git
And
curl https://install.meteor.com/ | sh
To deploy use meteor deploy to deploy to the meteor servers.
Look at mup by arunoda for deploying to your own server.
There's also demetorizer.