Featured post

About this blog

tuxThis blog was created with the idea of collecting and linking information about Linux, Git, how to set things up, how to tweak the system here and there, in different architectures, in different distributions and different releases.

All the information presented here is available to public knowledge and can be found with one, two, or a few more Google searches if you persist. All of them were used at least once on productive activities.

Please share your experience and share your comments.

Advertisements

Setting up mLab addon on Heroku

If you live outside the US or Europe, chances are you cannot provision some addons to your Heroku application. If you try to create one using the heroku config comand, you end up getting:

$ heroku addons:create mongolab:sandbox
Creating mongolab:sandbox on ⬢ radiant-stream-99649… !
▸ Please verify your account to install this add-on plan (please enter a credit card) For more information, see https://devcenter.heroku.com/categories/billing Verify now at
https://heroku.com/verify

The default heroku command: $ heroku addons:create mongolab:sandbox does not work.

If you try to add it from the web interface, same thing:

Screen Shot 2017-11-14 at 7.51.10 AM11-14-17

Although mLab MongoDB is a free add on, it is not possible to provision it without providing a credit card number

Even so, it is still possible to add the mLabs addon to your application on Heroku. You can do it via your mLabs account:

1) Head over to https://mlab.com and create an account or log in;

2) In the Home screen, click “Create new”:

create_new_db

2.1) Select ‘Sandbox (Free)’:

sandbox-free

2.2) Pick a region;
2.3) Give your DB a name;
2.4) Submit your order (should be $0.00)

Your DataBase should be created. Then go ahead and..

3) Click on your just-created DB;

4) Create a user:

create_db_user

5) After it has been created, use the information mLab gave you to fill out the MONGODB_URI variable line displayed above, replacing <dbuser> and <dbpassword>.

mlabs_guest

6) Set it up as a Heroku environment variable from your terminal :

You should then configure the environment variable by hand with:

$ heroku config:set [MONGODB_URI-provided-by-mLab]

in my case:

$ keroku config:set mongodb://mlabs_guest:<dbpassword>@ds264255.mlab.com:59255/test-database-d

This image shows how I set mine up for another project:

heroku_config_mongodb_uri

That should be it: now your MONGODB_URI is set and configured, and you can now connect it to heroku.

Good luck with your project,

Cheers!

Selecting remote branch on git

I recently started to work with two remote repositories on git, and then faced a probably common scenario: check the state of each repository (say ‘origin‘ and ‘vertiv‘).

A 20 minute search provided me the best solution:

$ git branch -u [remote-repo]/[branch]

For example:

git_st_remote

In this case, origin/master is ahead of vertiv/master by 2 commits, and my local is sync’ed with vertiv/master.

The docs read:

-u <upstream>, –set-upstream-to=<upstream>
Set up <branchname>’s tracking information so <upstream> is considered <branchname>’s upstream branch. If no <branchname> is
specified, then it defaults to the current branch.

Cheers!

Reference: https://stackoverflow.com/questions/23455842/how-can-i-make-git-status-check-two-different-remotes

Git: two awesome quick commands

Find branches the commit is on

git branch --contains <commit #>

Sample output:

Screen Shot 2017-10-17 at 10.18.41 PM10-17-17

fetch_weather, implement_axios and master all have the commit # 3dea5b6

Ref.: https://stackoverflow.com/questions/2706797/finding-what-branch-a-git-commit-came-from

Show all branches with unmerged commits to <branch>

git branch -a --no-merged <branch>

Sample output:

Screen Shot 2017-10-17 at 10.22.39 PM10-17-17

remotes/origin/error_handler has not yet been merged into master

Ref.: https://stackoverflow.com/questions/3600728/git-list-all-unmerged-changes-in-git

Happy git work!

Cheers!