Provide working MUP deployment template and guide #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This repo was great for getting a self-hosted version of Meteor APM up and running, but getting a properly configured server working well took a good deal of effort. During the time I was working through these issues along with @jasongrishkoff, it was clear that the issues would show up for most people attempting to self-host using this repo.
When I found this repo, I was looking for something I could clone, enter my server IP address/domain/ssh key, and hit
mup setup && mup deploy
to get it up and running.This PR is what I believe is the closest we can currently get to that goal. Using the setup provided via the example
mup.js
config and setup steps in README, I currently have a stable self-hosted APM server that uses HTTPS, uses minimal CPU/disk resources, and does everything I need it to. If I want to update/replace this server, it's a simple matter of runningmup deploy
again and it's reconfigured exactly as I need it.Using this new guide, somebody can spend ~30 minutes setting up their own fully functional APM server running on an AWS t2.nano instance for a whopping ~$5/month.