aawiseman

[out:json][timeout:25];
// gather results
(
  // query part for: “newer:"2015-10-09T19:01:00Z"”
  node(newer:"2015-10-09T19:01:00Z")({{bbox}});
  way(newer:"2015-10-09T19:01:00Z")({{bbox}});
  area(newer:"2015-10-09T19:01:00Z")({{bbox}});
  relation(newer:"2015-10-09T19:01:00Z")({{bbox}});
);
// print results

jpierson

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step)

   git clone [email protected]

t-book

# - Close port 8080 for inbound networking
# - Edit your local_settings to use proxy /geonode (and not port 8080)
# - Add following to local_settings: AVATAR_GRAVATAR_SSL = True
# - make sure mod_ssl is active: $ a2enmod ssl

# add let´s encrypt repository 
  $ sudo add-apt-repository ppa:certbot/certbot
  $ sudo apt-get update

# install certbot