meteor-up | Production Quality Meteor Deployment to Anywhere | Continuous Deployment library
kandi X-RAY | meteor-up Summary
kandi X-RAY | meteor-up Summary
Meteor Up is a command line tool that allows you to deploy any Meteor app to your own server. You can install and use Meteor Up on Linux, Mac and Windows. It can deploy to servers running Ubuntu 14 or newer. This version of Meteor Up is powered by Docker, making deployment easy to manage and reducing server specific errors. Read the getting started tutorial.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Set up the workers
- Update the meteor config .
- Prepares the Dockerfile for the package .
- Logs debug app to the server .
- Sets the shared proxy configuration
- Get the information about the current server
- Prepare the bundle .
- Retry authentication method
- Get the status of servers .
- Executes ssh .
meteor-up Key Features
meteor-up Examples and Code Snippets
server {
listen 80;
server_name example.com www.example.com;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
charset UTF-8;
server_name example.com www.example.com;
# meteor app
location / {
proxy_pass http://localho
module.exports = {
// rest of config
plugins: ['mup-redis'],
redis: {
// Server to run redis on.
servers: { one: {} },
// Version of redis. Add '-alpine' to use a much smaller docker image
version: '3.2.10-alpine'
}
}
mup se
mup deploy --config=mup-staging.json --settings=staging-settings.json
Community Discussions
Trending Discussions on meteor-up
QUESTION
First, thank you for reading my question. This is my first time on stackoverflow and I made a lot of research for answers that could help me.
CONTEXT
I'm developing a Meteor App that is used as a CMS, I create contents and store datas in mongoDb collections. The goal is to use these datas and a React project to build a static website, which is sent to an AWS S3 bucket for hosting purpose.
I'm using meteorUp to deploy my Meteor App (on an AWS EC2 instance) and according to MeteorUp documentation (http://meteor-up.com/docs.html#volumes), I added a docker volume in my mup.js:
...ANSWER
Answered 2021-Oct-06 at 13:35!!!!! UPDATE !!!!!
I found the solution!
In fact I had to check few things on my EC2 with ssh:
once connected, I had to go to '/opt/front/' and try to build the React-app with 'npm run build' I had a first error because of CHMOD not set to 777 on that directory (noob!) then, I had an error because of node-sass. The reason is that my docker is using Node v8, and my EC2 is using Node v16.
I had to install NVM and use a Node v8, then delete my React-App node_modules (and package-lock.json) then reinstall it.
Once it was done, everything worked perfectly!
I now have a Meteor App acting as a CMS / Preview website hosted on an EC2 instance that can publish a static website on a S3 bucket.
Thank you for reading me!
QUESTION
A Meteor app created locally on a Windows 10, uses Meteor Up to deploy to a Ubuntu VPS. The app is running and accessable from the browser 185.148.129.235.
The server code reads the names of the files in a directory located in '/var/www/html/Audio' where an Apache serves its content to client browser, but please note the error below.
Also here is the mup.js file, Any help is much appricated to be able fix this error and read the names of the files in said locatioin.
...ANSWER
Answered 2021-Feb-26 at 17:06Aftre reading up on Docker volumes, the following addition to the mup.js fixed the problem
QUESTION
I am running into a file upload error with files > 10M. I have followed the advice here: http://meteor-up.com/docs.html#advanced-configuration which says how to set it in the nginx proxy by setting the clientUploadLimit: '50M'
I pushed the changes using mup proxy reconfig-shared
, and it told me it had restarted the proxy. It didn't work, I still get the 413 (Request Entity Too Large) error.
I checked inside the nginx-proxy docker instance, and the file /etc/nginx/conf.d/my_proxy.conf
has the correct entry client_max_body_size 50M
. I restarted the EC2 box to make sure, but it's still not working.
This article https://www.tecmint.com/limit-file-upload-size-in-nginx/ suggests that the setting needs to go inside a http block, like this:
...By default, Nginx has a limit of 1MB on file uploads. To set file upload size, you can use the client_max_body_size directive, which is part of Nginx’s ngx_http_core_module module. This directive can be set in the http, server or location context.
ANSWER
Answered 2020-Sep-15 at 21:08Now this is speculation but have you tried going to the docker container's root shell changed the permissions to give write permission to root or your user chmod 760 /etc/nginx/nginx.conf
and edit the nginx file there?
QUESTION
basically i can't get my local or hosted mongo to connect to my app when running on meteor run android-device
. both local and hosted work fine with just meteor run
. i'm also unable to get this to run on the app published for testing to the play store but i assume once i'm able to run my hosted mongo locally i should be able to apply those fixes to the published version. i'm running ubuntu 18.04.
connecting to my local mongo when testing locally on my android phone:
so from what i’ve read online, the device and computer need to be on the same wifi network and i need to declare --mobile-server.
i’ve got my phone on airplane mode connected to the wifi network and plugged into my laptop for testing. i don’t believe this is a firewall issue because i have other hardware i’m connecting to this way for work.
these are the various scripts i’ve tried but none work. i’m at a complete loss! i’m running the latest meteor. anything in bold i’ve also tried on an emulator.
"android-device-local": "MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 192.168.0.102"
<-- ip address of my laptop on my wifi network
"android-device-local": "MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 192.168.0.102:3000"
"android-device-local": "MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server locahost:3000"
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server locahost:27017”
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 127.0.0.1”
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 127.0.0.1:27017”
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 127.0.0.1:3000”
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 192.168.0.109” <-- ip address of my phone on my wifi network
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server 192.168.0.109:3000”
“android-device-local”: “MONGO_URL=mongodb://:@localhost:27017/dbName meteor run android-device --mobile-server localhost:12816” <-- chrome’s remote debugging url
connecting to my hosted mongo (mongodb.com)
i do understand that the --mobile-server
here would be an online server that hosts your app, but this is where i get confused… if it’s hosted on the play store, what does this mean exactly? i have a personal website (domain registered on google, hosted on aws amplify) that i'm using a subdomain on for this purpose.
i’ve completed this guide https://sergelobatch.com/beginners-guide-to-deploying-a-meteor-app-to-an-aws-server-with-meteor-up/ and am able to access the app via the ec2 public ipv4 address and the subdomain through my web browser and it’s pulling data from the db as expected. i've allowed the public ipv4 of my ec2 access to my mongodb network. (sidenote, it's not https, does that matter?)
again running locally i’ve tried these, still with no luck:
“MONGO_URL= meteor run android-device --mobile-server :80”
“MONGO_URL= meteor run android-device --mobile-server :3000”
“MONGO_URL= meteor run android-device --mobile-server http://:80”
^^^ i've tried all the above with also ROOT_URL=sub.domain.com
“MONGO_URL= meteor run android-device --mobile-server sub.domain.com”
“MONGO_URL= meteor run android-device --mobile-server sub.domain.com:80”
UPDATE:
i do see that i'm getting not found for some cordova assets. even after adding these packages manually these persist.
ANSWER
Answered 2020-Jun-30 at 00:07for future reference: the fix was adding autoupdate and the necessary config via https://docs.meteor.com/packages/autoupdate.html and running dev with the flag --mobile server :80
and running build with --server :80
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install meteor-up
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page