paulsturgess.co.uk Report : Visit Site

Technical data of the paulsturgess.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host paulsturgess.co.uk. Currently, hosted in - and its service provider is - .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GitHub.com containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

web & ios dev – ruby, rails, rubymotion & react web & ios dev – ruby, rails, rubymotion & react paul sturgess rss index archives @paulsturgess github setup webpacker webpack-dev-server with docker-compose jan 9 th , 2018 the rails/webpacker gem is a fantastic way to configure webpack for your rails application. however, it has gone through quite a few different configuration options to get it working with docker. initially you could set the host by using command line arguments, but as of version 3.0.2 and this pull request the command line argument support was removed in favour of environment variables. by setting various environment variables you can override all dev server settings defined in config/webpacker.yml . so now my docker-compose.yml config looks something like this: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 web : << : *app command : /src/docker/web.sh ports : - "3000:3000" depends_on : - webpack environment : - webpacker_dev_server_host=webpack webpack : << : *app command : ./bin/webpack-dev-server ports : - 3035:3035 environment : - webpacker_dev_server_host=0.0.0.0 to install yarn and nodejs i added the following to my debian based dockerfile: 1 2 3 4 5 6 7 8 9 10 run apt-get update && apt-get install apt-transport-https run curl -ss https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \ && echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list \ && curl -sl https://deb.nodesource.com/setup_8.x | bash - run apt-get update && \ apt-get install -y \ yarn nodejs debug ruby using pry and docker compose jan 9 th , 2018 if you’re using docker and docker-compose you probably found that by default you can’t debug your ruby application with the binding.pry breakpoint. however, if you comment out the command line for your web container. then: 1 docker-compose up open a new tab and run: 1 docker-compose run --service-ports --rm web /the/command/you/commented/out then you will have interactive access to the command line with binding.pry ! ruby metaprogramming: define_method and instance_exec jan 9 th , 2018 this blog post runs through an example of iterating on some ruby code. the bizarre fictional scenario develops to make the requirements ever more complicated. there’s certainly many different ways to solve the underlying problem, but i wanted to show an example where define_method and instance_exec can be combined with class methods to make for some very powerful and concise code. for each change in requirements, i’ll post the code in full for how i’ve handled the new scenario. i will say upfront that these two metaprogramming methods should be used with caution. powerful and concise code does not necessarily make for easy to understand/debug/maintain code. the curry restaurant so, there’s a curry restaurant that sells vindaloo and tarka daal and there’s a customer that likes to order curry from the restaurant… bear with me :). upon receiving their meal, the customer will respond with a comment if the spiceyness isn’t to their taste. unfortunately the restuarant isn’t consistent with the spices it uses when cooking. with the above code we can do things like: 1 2 3 spicey_customer = spiceycustomer . new spicey_customer . order_tarka_daal spicey_customer . order_vindaloo if any of the meals are mild then the customer will respond with “that’s too mild!”. a new greedy customer then along comes another customer, a greedy one. they also like to order curry and comment on the meal. however, rather than comment on the spiceyness, they like to comment on the size of the portion. unfortunately the restuarant is also inconsistent with its porton sizes, but the greedy customer doesn’t care what type of curry it is, they just want it large! already we have a bit of duplication between the two customers but it’s not a massive problem at this point. a new menu item - jalfrezi the restaurant is doing really well and introduces a new jalfrezi curry to the menu. the greedy customer responds the same to it as for any curry, but the spicey customer responds to the jalfrezi, the same as when recieving a vindaloo - they want it hot! we’ve added order_jalfrezi to both customers and added expect_hot_curry to spiceycustomer because they respond the same for jalfrezi and vindaloo. now we really do have duplication between the two customers, so we’ll look at refactoring that next. refactor - dining out we decide that the two customers have enough shared behaviour to introduce a new module called diningout . this means both customers can order all three currys and then respond in a way that is specific to them. with the custom response defined in each customer in the respond_to_meal method. you might be thinking it would be better to make customer a class and have greedycustomer and spiceycustomer as subclasses that inherit from it, but for this example it doesn’t matter. this is a version of the template method pattern . we have our new diningout module and we’ve defined a respond_to_meal in both customers. this code is definitely cleaner but there is still a bit of a smell. if the restaurant expands with lots of new items on the menu and these customers need to respond differently, then the respond_to_meal method is going to get pretty big and complicated pretty quickly. we’re also very reliant on the name of the meal not changing. in addition the diningout module will bloat quickly with each new menu item. that isn’t a massive problem, but there’s already a fair bit of obvious duplication going on where the name of the order method closely matches the argument sent to order_meal . now you might be thinking, why can’t we just expose order_meal as a public method and call spiceycustomer.new.order_meal(:jalfrezi) instead of spiceycustomer.new.order_jalfrezi . however… a new fussy customer along comes the fussy customer who will only eat tarka daal and the newest item on the menu, chips. the fussy customer isn’t interested in responding to the meal and just eats in silence. in addition, the greedy customer will order chips, but the spicey customer would never order chips. sounds complicated doesn’t it? the simplest thing to do is to add an order_chips method to diningout and an empty respond_to_meal to the new fussycustomer . now we have some complicated rules and they’re not properly enforced. there’s nothing stopping us calling fussycustomer.new.order_vindaloo or spiceycustomer.new.order_chips even though neither of those customers would order those things. we could start putting some logic into the order_* methods to check the type of customer before ordering the meal, but that would get ugly fast. ideally we want a solution where we can tell by looking at the code which customer likes to eat which food and each customer wont even know how to order food they don’t want to order. introducing define_method and instance_exec before we get into the final solution, the end result is that we can now do things like the following: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 spicey_customer = spiceycustomer . new spicey_customer . order_tarka_daal spicey_customer . order_vindaloo spicey_customer . order_jalfrezi spicey_customer . order_chips # returns an undefined method error greedy_customer = greedycustomer . new greedy_customer . order_tarka_daal greedy_customer . order_vindaloo greedy_customer . order_jalfrezi fussy_customer = fussycustomer . new fussy_customer . order_chips fussy_customer . order_tarka_daal # returns an undefined method error also when we look at each customer we can see very clearly what they like to eat and how they like to respond for each menu item. the nice thing is that if the restaurant adds a new menu item, we don’t need to touch the diningout module at all. we just need to decide which customers would like to order the new menu item and how they might optionally respond. it works by defining a new class method eats . this method takes the name of the menu

URL analysis for paulsturgess.co.uk

http://paulsturgess.co.uk/blog/2016/10/19/how-to-write-and-test-a-stateless-react-component/
http://paulsturgess.co.uk/atom.xml
http://paulsturgess.co.uk/blog/2018/01/09/ruby-metaprogramming-define-method-and-instance-exec/
http://paulsturgess.co.uk/blog/2016/10/19/how-to-write-and-test-a-stateless-react-component/
http://paulsturgess.co.uk/blog/2016/11/06/how-to-write-and-test-a-redux-container-component-for-react/
http://paulsturgess.co.uk/blog/2017/04/29/using-enzyme-to-test-a-react-component-onclick-with-event-preventdefault/
http://paulsturgess.co.uk/blog/2018/01/09/using-pry-with-docker-compose/
http://paulsturgess.co.uk/blog/2018/01/09/setup-webpacker-webpack-dev-server-with-docker-compose/
http://paulsturgess.co.uk/blog/page/2/
http://paulsturgess.co.uk/blog/2017/02/01/using-capybara-and-phantomjs-to-test-an-external-website/
http://paulsturgess.co.uk/blog/2017/01/11/simple-method-for-checking-the-mime-type-for-a-file-in-ruby-on-rails/
http://paulsturgess.co.uk/blog/2017/02/08/making-and-testing-ajax-requests-with-axios-in-a-redux-app/
http://paulsturgess.co.uk/blog/archives
http://paulsturgess.co.uk/blog/2016/11/20/functional-programming-for-a-rubyist/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name:
paulsturgess.co.uk

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 10-Dec-2012

Registrar:
Fasthosts Internet Ltd [Tag = LIVEDOMAINS]
URL: http://www.fasthosts.co.uk

Relevant dates:
Registered on: 22-Mar-2003
Expiry date: 22-Mar-2019
Last updated: 20-Feb-2018

Registration status:
Registered until expiry date.

Name servers:
ns13.zoneedit.com
ns9.zoneedit.com

WHOIS lookup made at 05:12:46 30-Jul-2018

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2018.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS paulsturgess.co.uk

  PORT 43

  TYPE domain

DOMAIN

SPONSOR
Fasthosts Internet Ltd [Tag = LIVEDOMAINS]
URL: http://www.fasthosts.co.uk
Relevant dates:

  CREATED 22-Mar-2003

  CHANGED 20-Feb-2018

STATUS
Registered until expiry date.

NSERVER

  NS13.ZONEEDIT.COM 45.76.95.243

  NS9.ZONEEDIT.COM 45.77.82.193

  NAME paulsturgess.co.uk

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2018.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .