RebelMouse Talk to Us

This document is written to give an overview on how to work with your BitBucket on RebelMouse integration.

Using GIT

Since you are using your own GIT repository on Bitbucket which is totally separated from RebelMouse repository , you can maintain your repository as you wish. This allows for a lot of creative freedom in using the environment the way you'd like.

While you can use your own workflows, we still highly recommend our suggested workflow described in next steps.

I am new to GIT

Start by reading this GIT reference first http://gitref.org/. You can skip the part about "Getting and Creating Projects", everything else is quite useful.

Comparing GIT workflows

You can find a really good tutorial about different GIT workflows at https://www.atlassian.com/git/tutorials/comparing-workflows, which we highly recommend reading. especially Feature Branch Workflow. The most vital and necessary commands are listed in this tutorial as well.


Daily workflow example

As mentioned before Feature Branch Workflow is approach which we highly recommend to stick with. It means that for every new feature (or any bug you will fixing) you will create a new branch. All changes for that feature then should be in this branch. This way your master will be always clean and ready for syncing with our master.

This tutorial contains also other commands. Before start please read topics about VIM and Nano and Custom Roar Commands.

Switch to master branch, be sure that you are on it with git status. You can also check if there are any changes with git diff command.

git checkout master

Rebase the master. This will take down all changes (which other developers in your team have pushed to origin) from BitBucket repository to your local repo.

git pull --rebase

Fetch new changes. This will take down all changes (which other developers in our team have pushed to origin) from GitHub repository to your local repo.

roar-fetch

Check if there are any changes.

git status

If there are any changes you need to commit them.

git commit -am "updates from RM repo"

Push new changes from local master branch to your origin master branch.

git push origin master

Let's say you would like to start working on a new feature. Create a new feature branch. Please respect the TICKET_NO-lower_case_with_underscore naming.

git checkout -b 12345-new_branch_name

Open and edit file which you need to update. I will work on article.css with VIM terminal editor for this example.

vim static/css/roar/article.css

Every time you want to check your changes in browser you need to run roar-reload.

roar-reload

All templates are cached. This command reloads your environment and applies your recent changes; without running it you won't see any updates in the browser after refresh. You don't need to run this command when you've edited static files.

Check your beta in browser now. If you are satisfied with your changes and new feature looks okay, you should push this changes to your repo first.

Verify your changes one more time.

git diff

Commit your changes with meaningful commit message. Don't forget to include #TICKET_NO at the end.

git commit -am "updated colors on article page #12345"

Push changes to your repo.

git push origin 12345-new_branch_name

After this you are ready for pushing to stage server. Please note that you can push to stage server from any branch. Branch which you are currently on will be deployed to stage.

roar-push-stage stage_name

URL of stage server will be outputted in this step.

If everything looks okay, you can proceed with pushing to production. Pushing to production is possible only from master branch. Before that you need to fetch latest code from BitBucket and GitHub repo. This way you will be sure that your changes looks well even with latest code. It could happen that in meantime someone else has made changes in the same file you were working on. It is necessary that code is synced. You need to repeat the steps which we made in the beginning.

git checkout mastergit pull --rebaseroar-fetchgit statusgit commit -am "updates from RM repo"git push origin master

Then merge your feature branch into master.

git merge --no-ff 12345-new_branch_name

In most cases everything will be okay after this. But from time to time you will get merge conflicts. You will be notified about them in terminal and you need to solve them manually. This happens because someone else were working in the same time, on the same lines in the same file as you do.

Just before pushing changes live, please verify that everything still looks okay on your beta.

roar-reload

Check your beta in browser. If everything is okay, you're clear to push your updates live.

roar-push-prod "A meaningful message explaining new updates."

Deployment could be blocked by other developers at any given time and deploying itself could take up to 20 min. In this process your feature branch will be also pushed to BitBucket.

When deploying will be done, you are able to check your changes in browser on live site.

You're not required to stick with this workflow, but it is helpful. If you are good with GIT, you can use it on your own way. Then all you need to know are our 4 roar-[...] custom commands.

What Is RebelMouse?
Request a Proposal
subscription model for publishers
Content Strategy

In 2022, Publishers Take Back Control With Subscription Success

Users are ready to pay for content that delivers

The Rise of the Mature User

It's been a long and winding path, but in 2022 the subscription model continues its upward trajectory as a top revenue strategy for publishers of all sizes. The tug of war between platforms and publishers reached its peak in the last few years of the previous decade, leaving users desperate for a modern user experience that's clear of any clutter from the duopoly that is Google and Facebook. This is why intelligent paywall models are a top choice for users looking to consume content right from the source. When done correctly, the strategy can work for any type of media. The New York Times, a frequent showpiece example of the power of paywalls, is constantly reporting record-busting subscription numbers, with 7.6 million digital subscriptions in 2021.

And it all makes perfect sense. The subscription model eliminates the middleman — such as the platforms — so readers get the experience and content they want, and publishers get the cash they need.

Keep reading... Show less
People on a train station
Rebel Insights

RebelMouse Q1 2021 Platform Updates

Speed, performance, and Core Web Vitals enhancements

Click here to read our Q2 2021 platform performance updates!

At RebelMouse, we pour our souls into making sure that our platform is always the most modern, high-performance CMS on the market. In fact, we invested over $100,000 worth of hours into our platform in Q1 2021 alone. This has resulted in updates and performance enhancements that publishers would have to pay for on their own to make happen on any other platform, such as WordPress. We're proud to be at a level of scale where we can invest this way into our platform, and we will continue to invest at this rate every quarter moving forward just as we have in the past.

Here are the major updates that we've added to the platform in Q1.

Keep reading... Show less
Interested in a Free Website Health Check?Check Your
Website's Health
Get Your Free Analysis Now
Google Says They’re Increasing Communication About Algorithm Updates
Rebel Insights

Google Says They’re Increasing Communication About Algorithm Updates

If you feel like you’ve been hearing about updates from Google more often, it’s not just in your head. During a recent Google Meetup in NYC, Search Liaison Danny Sullivan said that Google hasn’t been launching more updates lately, but it has made a point to communicate about its updates to users more frequently.

Even though you may know when updates are happening more than before, you still won’t know about every little change that Google makes. In a post about the topic, Sullivan said that Google’s algorithm is updated thousands of times a year. Many of these incremental updates are so small that users and site owners won’t even know they are happening. Together, these minor updates add up to enhance Google’s search experience overall.
Keep reading... Show less
New Report: Email Is a ‘Key Tool’ for Building Loyalty
Rebel Insights

New Report: Email Is a ‘Key Tool’ for Building Loyalty

For the first time ever, the Digital News Report authored by Reuters Institute for the Study of Journalism has dedicated an entire chapter to news consumption via email. The report analyzed data from thousands of readers of online news across 46 different markets. While the insights around email are focused on news content specifically, the data is useful for any publisher looking to enhance a newsletter strategy or even launch a new campaign. The findings in this year’s report shows that email continues to rise in popularity as an effective way to reach hyper-targeted audiences.

Who Reads Email Newsletters?

While email is not the primary source of traffic for most news outlets, it is more popular in the U.S. than in other countries. This year’s Digital News Report found that 22% of users surveyed in the U.S. use newsletters or email alerts, with almost half of them saying it is their main way of accessing digital news.

Keep reading... Show less
Build on a Better PlatformReady to See More?
Request a Proposal